Developer delegate: dev.bitsharesblocks

Started by svk, November 12, 2014, 01:46:01 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

svk

I've shut down the client on the bitsharesblocks server to free up memory in order to try to upgrade to v0.4.25, the API is still running but there won't be any new data for a while!
Worker: dev.bitsharesblocks

liondani

current block should be easier to find...
(bold or/and other color maybe?)
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

svk

Quote from: liondani on December 11, 2014, 08:31:18 PM
Quote from: svk on December 11, 2014, 05:09:47 PM
Quote from: liondani on December 11, 2014, 10:00:06 AM

>> blockchain_unclaimed_genesis

1,103,261,944.56647 BTS


On bitsharesblocks says that the unclaimed is:  604,259,426 BTS   
please fix  ;)

My client actually returns this on v0.4.25-RC1:

(wallet closed) >>> blockchain_unclaimed_genesis
603,148,674.73703 BTS
(wallet closed) >>> blockchain_calculate_supply
asset: BTS
2,498,278,726.84378 BTS


Compiling RC2 now to see if that's better.

on v0.4.25-RC2:

(wallet closed) >>> blockchain_unclaimed_genesis
603,148,674.73703 BTS
[


on v0.4.24.1:

>> blockchain_unclaimed_genesis

1,102,151,193.48926 BTS


that should not happen....

The reason is that the vested balances of 500 million BTS are no longer counted as unclaimed.
Worker: dev.bitsharesblocks

liondani

Quote from: svk on December 11, 2014, 05:09:47 PM
Quote from: liondani on December 11, 2014, 10:00:06 AM

>> blockchain_unclaimed_genesis

1,103,261,944.56647 BTS


On bitsharesblocks says that the unclaimed is:  604,259,426 BTS   
please fix  ;)

My client actually returns this on v0.4.25-RC1:

(wallet closed) >>> blockchain_unclaimed_genesis
603,148,674.73703 BTS
(wallet closed) >>> blockchain_calculate_supply
asset: BTS
2,498,278,726.84378 BTS


Compiling RC2 now to see if that's better.

on my v0.4.25-RC2 server:

(wallet closed) >>> blockchain_unclaimed_genesis
603,148,674.73703 BTS
[


on my v0.4.24.1 server:

>> blockchain_unclaimed_genesis

1,102,151,193.48926 BTS


that should not happen(!)....
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

clayop

Quote from: svk on December 11, 2014, 05:35:52 PM
Quote from: clayop on December 11, 2014, 05:17:26 PM
Can you add a function that show availability of price feeds from marginal delegates, say rank 102~201?

They're showing now in the overview table.

Cool. Thanks  +5%
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

svk

Quote from: clayop on December 11, 2014, 05:17:26 PM
Can you add a function that show availability of price feeds from marginal delegates, say rank 102~201?

They're showing now in the overview table.
Worker: dev.bitsharesblocks

clayop

Can you add a function that show availability of price feeds from marginal delegates, say rank 102~201?
Bitshares Korea - [url="http://www.bitshares.kr"]http://www.bitshares.kr[/url]
Vote for me and see Korean Bitshares community grows
delegate-clayop

svk

Quote from: liondani on December 11, 2014, 10:00:06 AM

>> blockchain_unclaimed_genesis

1,103,261,944.56647 BTS


On bitsharesblocks says that the unclaimed is:  604,259,426 BTS   
please fix  ;)

My client actually returns this on v0.4.25-RC1:

(wallet closed) >>> blockchain_unclaimed_genesis
603,148,674.73703 BTS
(wallet closed) >>> blockchain_calculate_supply
asset: BTS
2,498,278,726.84378 BTS


Compiling RC2 now to see if that's better.
Worker: dev.bitsharesblocks

svk

Quote from: liondani on December 11, 2014, 04:45:52 PM
When a stand by delegate has not produced a single block, reliability field should not show 0% and red but something like:

a) uknown,
b) n/a, 
c) ? , 
d) - ,
etc.

and.. green

Yea agreed, I'll add something like this.
Worker: dev.bitsharesblocks

liondani

When a stand by delegate has not produced a single block, reliability field should not show 0% and red but something like:

a) uknown,
b) n/a, 
c) ? , 
d) - ,
etc.

and.. green
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

svk



Quote from: toast on December 11, 2014, 12:37:26 AM
It would be neat if you issued BTSBLOCK which was redeemable for a set fraction of your total ad bandwidth. With the coming asset ownership restriction option, you can do it legally.

I don't have any ad revenue though ;) I might just issue an asset though and maybe someday it'll become useful..
Worker: dev.bitsharesblocks

svk



Quote from: arhag on December 11, 2014, 06:45:38 AM
Here are some additional features I would eventually love to see on bitsharesblock.com:

  • Look up the details of a transaction by transaction ID. List all of the operations the transaction does (withdraw this amount from this balance, deposit this much to this balance, etc.).
  • Look up details and history of a given balance ID. See what conditions need to be satisfied to withdraw from that balance (signature for which address, multisig, etc.). Look at the history of transactions (with transaction ID links) that have deposited or withdrawn funds from that balance (similar to blockchain.info).
  • Look up history of JSON public data updates for any given BTS account.

Noted, will get to this eventually!
Worker: dev.bitsharesblocks

svk

Quote from: liondani on December 11, 2014, 10:00:06 AM

>> blockchain_unclaimed_genesis

1,103,261,944.56647 BTS


On bitsharesblocks says that the unclaimed is:  604,259,426 BTS   
please fix  ;)
Very strange, I'll check it out when I get home, thanks!
Worker: dev.bitsharesblocks

liondani


>> blockchain_unclaimed_genesis

1,103,261,944.56647 BTS


On bitsharesblocks says that the unclaimed is:  604,259,426 BTS   
please fix  ;)
[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

arhag

Here are some additional features I would eventually love to see on bitsharesblock.com:

  • Look up the details of a transaction by transaction ID. List all of the operations the transaction does (withdraw this amount from this balance, deposit this much to this balance, etc.).
  • Look up details and history of a given balance ID. See what conditions need to be satisfied to withdraw from that balance (signature for which address, multisig, etc.). Look at the history of transactions (with transaction ID links) that have deposited or withdrawn funds from that balance (similar to blockchain.info).
  • Look up history of JSON public data updates for any given BTS account.