Author Topic: !!! Stupid Questions Thread !!!  (Read 251405 times)

0 Members and 1 Guest are viewing this topic.

Offline vlight

  • Sr. Member
  • ****
  • Posts: 275
    • View Profile
  • BitShares: vlight
I pressed that green 'cover' button and it does not work. Nothing happens. Why?

Using BitShares 0.4.24 win32 64-bit wallet.

EDIT: nvm it works with the latest GUI update  ;)
« Last Edit: November 12, 2014, 08:56:49 pm by vlight »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc

Offline davidpbrown

฿://1CBxm54Ah5hiYxiUtD7JGYRXykT5Z6ZuMc

Offline svk

What's the difference now between
https://github.com/dacsunlimited/bitsharesx/releases/
and
https://github.com/BitShares/bitshares/releases

I've got so used to using dacsunlimited and I can't recall why. Is it that dacsunlimited still is the only one working for Linux?

No you should only be using https://github.com/BitShares/bitshares/releases now.
Worker: dev.bitsharesblocks

Offline davidpbrown

What's the difference now between
https://github.com/dacsunlimited/bitsharesx/releases/
and
https://github.com/BitShares/bitshares/releases

I've got so used to using dacsunlimited and I can't recall why. Is it that dacsunlimited still is the only one working for Linux?
฿://1CBxm54Ah5hiYxiUtD7JGYRXykT5Z6ZuMc

Offline pc

  • Hero Member
  • *****
  • Posts: 1530
    • View Profile
    • Bitcoin - Perspektive oder Risiko?
  • BitShares: cyrano
I'm trying to wrap my head around the effect of merchant adoption on bitusd.

With Bitcoin, this puts selling pressure on the Bitcoin price. Btc being converted to fiat by auto selling.


But how would this work with Bitusd or any other asset?

Let's say the merchant wants to convert their assets to fiat.
Would this result in selling pressure on the bitassets and thus buying pressure on BTS(x)?

I think you can't really compare BTC and BitUSD in that regard. There's two important differences:
1. BitUSD is less volatile, so there is less pressure to get rid of them immediately to avoid a loss.
2. The BTC used for buying things are (at least in part) not bought on the market, they stem from mining or from long-term holders. So there is no equivalent buying pressure to counter the selling pressure. BitUSD OTOH must be bought (or shorted) before it can be spent. So there is always a near-equilibrium for buying and selling BitUSD.
Bitcoin - Perspektive oder Risiko? ISBN 978-3-8442-6568-2 http://bitcoin.quisquis.de

Offline graffenwalder

I'm trying to wrap my head around the effect of merchant adoption on bitusd.

With Bitcoin, this puts selling pressure on the Bitcoin price. Btc being converted to fiat by auto selling.


But how would this work with Bitusd or any other asset?

Let's say the merchant wants to convert their assets to fiat.
Would this result in selling pressure on the bitassets and thus buying pressure on BTS(x)?



jakub

  • Guest
I am trying to understand how the voting mechanism works in the Bitshares client.
I have these questions:

1. In the GUI in the "Delegates" section there are two tabs: "All Delegates" and "My Votes" and my question refers to the second tab: How do I manage the list in "My Votes" tab? How do I add and remove delegates in this list?

2. In the GUI in every account I have the "Vote" tab and there seems to be a table below which is empty. How do I populate this table?

3. In the console, when I run wallet_account_vote_summary I get "No votes found". How do I add votes to this one? I have a couple of delegates which I have approved (by using wallet_account_set_approval) but why don't they show up in wallet_account_vote_summary? Also, wallet_check_vote_proportion returns only zeros - how do I change that?

Maybe there is a Wiki on this subject? I could not find one.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
unconfirmed transactions are not taken into account during the snapshot .. so the corresponding amounts would be book for the OLD (payee) address ..

Offline montpelerin

  • Jr. Member
  • **
  • Posts: 37
    • View Profile
This question has also been posted in the Snapshot Notice thread:
https://bitsharestalk.org/index.php?topic=10290.msg145254#msg145254

I am guessing the answer will apply to more than one of us here.

I sent several PTS transactions to new addresses about midday yesterday (local wallet to local wallet).
Most have gone through but a few remain unconfirmed.

Which address will the snapshot adhere to (regarding the unconfirmed transactions)- the sender address or the recipient address?

Thanks.
« Last Edit: November 05, 2014, 10:02:55 pm by montpelerin »

Offline fuzzy

Are you on version 4.23.1? I had this issue until updating to that version.
done...
and...
fixed....for now.
WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline Riverhead

Are you on version 4.23.1? I had this issue until updating to that version.

Offline fuzzy

I am certain this has been asked before, but since I am having trouble knowing what exactly to ask to bring it up....i'm going to post here.  My wallet sometimes syncs up with the network and at other times it sits there for days without doing so.  Usually when it does, it takes a seemingly random amount of time to do so...ranging anywhere from 15 minutes to 5 hours.  Lately it has not synced up with the network at all. 

I am thinking I might need to add some nodes?  Is this correct? 

If yes, can someone copy/paste an answer? 

If no, what else am I missing?
I noticed some other uses in the forums complaining about the exact same thing
It seems to me that the network code has some dead lock somewhere such that it will not connect to the seed nodes ..
not sure though ..

over here, once I am connected to the network all is fine and stays that way .. (but I am on Linux)

So I take it there is no fixing this at the moment?  :/
WhaleShares==DKP; BitShares is our Community! 
ShareBits and WhaleShares = Love :D

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani

yep .. the block confirmation time is fixed to 10 seconds .. no matter the transaction types ..

and that means practical an average of 5 seconds!!! ;)


Sent from my ALCATEL ONE TOUCH 997D
« Last Edit: November 02, 2014, 03:25:51 pm by liondani »

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
with the merger and all applications within one blockchain, will the confirmation times and transactions be as fast as they are now?
yep .. the block confirmation time is fixed to 10 seconds .. no matter the transaction types ..