go through toast's recent posts and read about the balanceid of each UTXO that is NOT a address to send funds to but can be used to identify an address where you could send dividends to .. topic was opened by monsterer and is called sth with refund or so .. cant xpost atm

yup i think i've figured it out, i've tested it with bts and bitusd, now all i have to do is write something that can log all of the various send/receives of that specific asset in order to tally them up, then i can just send the right amount of whatever to the 'owner' of each
wallet_transfer_to_address 1 USD myaccount ownerspublicaddress
unless this is not the proper way to do it? (it worked, but not sure if there is a better way?)

Hey, I'm wondering if there is a way to set up an asset that pays out dividends to all of the people who have shares, based on how many shares they have?
for example if i have a user issued asset called BLAH that has 10,000 shares unevenly distributed to 5 users:
user1 6000
user2 1500
user3 1000
user4 1000
user5 500

is there a way to get this information by querying the bitshares client?

those two commands are nearly identical, only difference is the second one also installs zlib1g-dev
the use of \'s is just to make it more human readable on a console without scrolling sideways

Possible dumb question.. Trying to register at the faucet, I get this:
 
We were unable to register account 'kencode' - { "message": "Assert Exception (10)\nbase58str.substr( 0, prefix_len ) == prefix: \n", "detail": "10 assert_exception: Assert Exception\nbase58str.substr( 0, prefix_len ) == prefix: \n {\"base58str\":\"1A0499F885706D41559650D832FBB0E291EA53A1\"}\n th_a types.cpp:31 public_key_type", "code": 10 }
 
Is that err saying my pgp fp is not correct? i entered the shorter 64-bit version too, just in case. no go.
Thanx
  -ken

try this in your wallet:

go to the console button
type in:
wallet_get_account_public_address yourusername

(yourusername as in your username )
it should pump out a public key address
that should be what the site wants

Hello,
I'm implementing Bitshares client and encounter a issue with BTS address validating rpc call:
the rpc call validate_address only work for account key and not for BTS addresses (account public address or addresses created by calling wallet_address_create accountName).
- validate_address accountKey : return true
- validate_address BTSaddress , it always return false
I need to validate BTS address
Any help is appreciated, thanks a lot.

have you tried looking at:
wallet_get_account <bts public name>
wallet_get_account_public_address <bts public name>

i believe this is exactly what you want.

>>> wallet_get_account_public_address asfdasdfsfdsfasfsafsdfsdfs
20006 unknown_account: unknown account
Unknown account name!
    {"account_name":"asfdasdfsfdsfasfsafsdfsdfs"}
    th_a  wallet.cpp:1315 get_account

    {}
    th_a  wallet.cpp:1334 get_account

    {"account_name":"asfdasdfsfdsfasfsafsdfsdfs"}
    th_a  wallet_api.cpp:771 wallet_get_account_public_address

    {}
    th_a  common_api_client.cpp:4575 wallet_get_account_public_address

    {"command":"wallet_get_account_public_address"}
    th_a  cli.cpp:579 execute_command

>>> wallet_get_account_public_address yaksbeard
BTS7GQB9CABxXKLGmP75b6sBc1DhsRtHGfHY

When I go to Accounts to check the Estimated Yield for my BitShares, there's never anything there.  Should there be?  If not, how do I find out the interest rate/rate of return on my BitShares?  Any help will be greatly appreciated.  Thanks.

like people have said there is no yield on bitshares themselves, but on the bitassets in bitshares (for example bitusd)
i'm super new here so only really starting to get a decent handle on things, i've noticed the wiki entries sometimes are pretty outdated and such, but here is the entry relating to bitassets http://wiki.bitshares.org/index.php/BitShares/bitAssets and in there you can see a specific example of yield with the bitusd asset

Yield on BitAssets

BitAssets will now yield a return for their owners from the transaction and market fees involving that asset. This is a variable yield and not a guaranteed ROI. It will be payed on any bitAsset, not just the bitUSD, but for the sake of simplicity the following will describe the mechanics by means of the bitUSD.

Users will not have to do anything to benefit from this yield, it will automatically show up in their balance and transaction records as part of normal use. Every time you make a transaction that withdraws from one of your balances it will pay any yield due back to that balance.

The yield can be calculated as:

ACCOUNT_BALANCE / BIT_ASSET_SUPPLY  *  TOTAL_ACCUMULATED_FEES * PERCENT_OF_YEAR_HELD

After 1 year you hit the maximum yield percent. Simply move your funds once per year and you can see the maximum benefit.

You can estimate the "current APR" as

TOTAL_ACCUMULATED_FEES / BIT_ASSET_SUPPLY.

The following things can reduce the current yield estimate
    New BitUSD being created with a market fee less than (TOTAL_ACCUMULATED_FEES / BIT_ASSET_SUPPLY)
    Someone cashing out some of their yield.

The following things can increase the current yield estimate
    Market Transactions with more overlap than (TOTAL_ACCUMULATED_FEES / BIT_ASSET_SUPPLY)
    Transactions with BitUSD fees paid.

So what kind of yield can one expect to see?
    $0.05 per transaction, 0.01% or more BitUSD trade volume. Up to 10% on new BitUSD issuance based upon existing demand. Perhaps less.
    Assume we get to 1 TPS in BitUSD the network would earn $1.5 million from transaction fees, if there were $15M BitUSD in circulation then that would be a 10% yield. Every time someone submits / cancels a bid with BitUSD it counts as a transaction. $15M BitUSD in circulation would mean $30M BTSX locked up as collateral.

i'm not sure how much of that is 'current' but its probably a good starting point, as well as the post on the forums here:
https://bitsharestalk.org/index.php?topic=8520.msg110779#msg110779

as an example tho, yesterday i traded some bitshares for bitusd in the client (27bitusd), today my client is saying this: (keep in mind i transferred some of my bitusd to a friend to show him how it worked so its not exactly 27 anymore)



i'm not sure at what time i did the exchanging to bitusd, but i think it was at about 8am est, so i'm guessing that yield is not completely *accurate* for a full day.


hope this helps you out a little bit.
edit: just as i posted this i looked at my client and it is now 0.0007 estimated yield