BitShares Forum
Main => General Discussion => Topic started by: bytemaster on September 03, 2014, 03:01:30 pm
-
Delegates for future reference and to help people vote I will require everyone I vote for to publish their version number in the public data associated with their account.
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
This version number will be displayed under your delegate name on the delegates page. I will use this rather than a forum thread to decide future voting/approval.
daslab and delegate.nathanhourt.com are already doing this.
-
I like it. Updated.
-
updated：
dnsdac
w.dnsdac
-
Active delegates spartako,spartako1,spartako2 updated:
default (unlocked) >>> blockchain_get_account spartako
Name: spartako
Registered: 2014-07-19T18:00:20
Last Updated: 60 seconds ago
Owner Key: BTSX5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC
Active Key History:
- BTSX5mgup8evDqMnT86L7scVebRYDC2fwAWmygPEUL43LjstQegYCC, last used 46 days ago
ID NAME (* next in line) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
============================================================================================================================
335 spartako 10.30631730 % 3255 128 96.22 % 50 % 2,445.21213 BTSX 390097
Public Data:
{
"version": "0.4.11"
}
default (unlocked) >>> blockchain_get_account spartako1
Name: spartako1
Registered: 2014-07-19T18:01:50
Last Updated: 61 seconds ago
Owner Key: BTSX5Ar4j53kFWuEZQ9XhxbAja4YXMPJ2EnUg5QcrdeMFYUNMMNJbe
Active Key History:
- BTSX5Ar4j53kFWuEZQ9XhxbAja4YXMPJ2EnUg5QcrdeMFYUNMMNJbe, last used 46 days ago
ID NAME (* next in line) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
============================================================================================================================
338 spartako1 10.38169401 % 3563 125 96.61 % 50 % 2,614.43688 BTSX 389984
Public Data:
{
"version": "0.4.11"
}
default (unlocked) >>> blockchain_get_account spartako2
Name: spartako2
Registered: 2014-07-19T18:01:50
Last Updated: 52 seconds ago
Owner Key: BTSX64P4Tij8F4CEvAiS9bheNs9vGoUESjKT61Va6cdoHGVsBMtN1H
Active Key History:
- BTSX64P4Tij8F4CEvAiS9bheNs9vGoUESjKT61Va6cdoHGVsBMtN1H, last used 46 days ago
ID NAME (* next in line) APPROVAL PRODUCED MISSED RELIABILITY PAY RATE PAY BALANCE LAST BLOCK
============================================================================================================================
337 spartako2 9.86739994 % 3622 132 96.48 % 50 % 2,682.23560 BTSX 390040
Public Data:
{
"version": "0.4.11"
}
default (unlocked) >>>
-
Delegates for future reference and to help people vote I will require everyone I vote for to publish their version number in the public data associated with their account.
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
This version number will be displayed under your delegate name on the delegates page. I will use this rather than a forum thread to decide future voting/approval.
daslab and delegate.nathanhourt.com are already doing this.
Is there an official 0.4.11 version ?
Shouldn't version tagging be restricted to only official versions?
Isn't it better to provide revision (hash) ?
-
Delegates for future reference and to help people vote I will require everyone I vote for to publish their version number in the public data associated with their account.
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
This version number will be displayed under your delegate name on the delegates page. I will use this rather than a forum thread to decide future voting/approval.
daslab and delegate.nathanhourt.com are already doing this.
Is there an official 0.4.11 version ?
Shouldn't version tagging be restricted to only official versions?
Isn't it better to provide revision (hash) ?
No official 0.4.11 version yet.
-
Delegates for future reference and to help people vote I will require everyone I vote for to publish their version number in the public data associated with their account.
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
This version number will be displayed under your delegate name on the delegates page. I will use this rather than a forum thread to decide future voting/approval.
daslab and delegate.nathanhourt.com are already doing this.
Is there an official 0.4.11 version ?
Shouldn't version tagging be restricted to only official versions?
Isn't it better to provide revision (hash) ?
No official 0.4.11 version yet.
I'm runnning with 0.4.11-RC1, I have to change version to: { "version":"0.4.11-RC1" } ?
-
Delegates for future reference and to help people vote I will require everyone I vote for to publish their version number in the public data associated with their account.
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
This version number will be displayed under your delegate name on the delegates page. I will use this rather than a forum thread to decide future voting/approval.
daslab and delegate.nathanhourt.com are already doing this.
Is there an official 0.4.11 version ?
Shouldn't version tagging be restricted to only official versions?
Isn't it better to provide revision (hash) ?
No official 0.4.11 version yet.
If I use specific version - should I rely on "info" command ?
If there is no official version - why should anyone publish 0.4.11 ?
Lets just establish guidelines for this (for example: users should use the version from "info", or all revisions after <hash> are considered 0.4.11 ).
-
Updated.
Why not check whether the input version matches the one got by 'info' command? It can help avoid faking input or typo.
-
Updated.
Why not check whether the input version matches the one got by 'info' command? It can help avoid faking input or typo.
The version specified in this thread: https://bitsharestalk.org/index.php?topic=8147.0 (https://bitsharestalk.org/index.php?topic=8147.0) shows 0.4.10 in the "info" command output. However it is referenced by Bytemaster as 0.4.11 .
-
Updated:
delegate1-galt
delegate1.john-galt
with current 4.10 version.
-
Updated.
-
Updated delegate alecmenconi with version: 0.4.10.
Will look at updating to 0.4.11 tonight.
-
*.delegate.xeroc
up-to-date and version field available
-
updating
-
Done delegate.coinhoarder
-
update to 0.4.11
hear.me.roar.lion
fire.and.blood.dragon
my.watch.begins.nightswatch
============================================================================================================================
10274 hear.me.roar.lion 10.05342676 % 182 2 98.91 % 100 % 439.67254 BTSX 390821
Public Data:
{
"version": "0.4.11"
}
-
Updated. I've also added the version information to the delegates overview on my site, that way you can get a quick visual overview :)
http://bitsharesblocks.com/delegates
-
Delete cube updated.
-
calabiyau
neuronics
version published
-
wackou-delegate version published
-
I updated delegate node registration as instructed. However I think manually publishing versions is unnecessary and should be done automatically by node itself on upgrade. This would avoid unnecessary, error prone actions by delegates.
-
(http://robohash.org/set_1/delegate.liondani?size=75x75)delegate.liondani published (version 0.4.10 , 77%)
liondani (unlocked) >>> wallet_account_update_registration delegate.liondani delegate.liondani { "version":"0.4.10" } 77
{
"expiration": "20140903T214456",
"delegate_slate_id": null,
"operations": [{
"type": "withdraw_op_type",
"data": {
"balance_id": "BTSXAszsiqqWE6Gd7cRjVY1YQcRvHQtDkex7R",
"amount": 10000,
"claim_input_data": ""
}
},{
"type": "update_account_op_type",
"data": {
"account_id": 10493,
"public_data": {
"version": "0.4.10"
},
"active_key": null,
"delegate_pay_rate": 77
}
}
],
"signatures": [
"20e53e082d2c4055c3a0eacc858ae738165d57d13357a06093e7437b01d779381c4e0270647f61c818eed24f6cafc93d99974f37f9c1516458e914afcdd36721a2",
"2044da73b3b98df8c1619a17586f4b7ee62ceab657e114532d79d5c349966d0f0010edbe80bf8b3b779b5b18d6d4064c857860757f8231009badda4562b70730e9"
]
}
liondani (unlocked) >>> info
{
"blockchain_head_block_num": 392142,
"blockchain_head_block_age": "2 seconds old",
"blockchain_head_block_timestamp": "2014-09-03T20:46:50",
"blockchain_average_delegate_participation": "100.00 %",
"blockchain_confirmation_requirement": 1,
"blockchain_accumulated_fees": "310,048.44794 BTSX",
"blockchain_delegate_pay_rate": "2.56323 BTSX",
"blockchain_share_supply": "1,999,912,280.05465 BTSX",
"blockchain_blocks_left_in_round": 41,
"blockchain_next_round_time": "at least 7 minutes in the future",
"blockchain_next_round_timestamp": "2014-09-03T20:53:40",
"blockchain_random_seed": "669112a73d69a6472369f55e4be74796108cc47a",
"client_data_dir": "/home/liondani/.BitSharesX",
"client_version": "0.4.10",
"network_num_connections": 20,
"network_num_connections_max": 200,
"ntp_time": "2014-09-03T20:46:52",
"ntp_time_error": -0.015671999999999998,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "2 years 10 months in the future",
"wallet_unlocked_until_timestamp": "2017-06-27T18:17:01",
"wallet_last_scanned_block_timestamp": "2014-09-02T13:54:50",
"wallet_scan_progress": "? %",
"wallet_block_production_enabled": true,
"wallet_next_block_production_time": "at least 7 minutes in the future",
"wallet_next_block_production_timestamp": "2014-09-03T21:03:40"
}
-
I updated delegate node registration as instructed. However I think manually publishing versions is unnecessary and should be done automatically by node itself on upgrade. This would avoid unnecessary, error prone actions by delegates.
Yeah, considering that would generate a transaction / fee I didn't want it to be "automatic". We are considering an RPC call to reduce potential errors.
-
done
delegate*.xeldal
version 0.4.10
-
I updated delegate node registration as instructed. However I think manually publishing versions is unnecessary and should be done automatically by node itself on upgrade. This would avoid unnecessary, error prone actions by delegates.
Yeah, considering that would generate a transaction / fee I didn't want it to be "automatic". We are considering an RPC call to reduce potential errors.
+5% Since it can be displayed by get_info, it should be done automatically. Probably the Delegate Window need to show more information, like version, payrate, published price feeds... just like this website. http://www.bitsharesblocks.com/delegates
-
Done updating.
bts.coin
e.coin
bimin.coin
-
update done
-
sun.delegate.service
moon.delegate.service
updrage : {version:0.4.10}
-
Updated. I've also added the version information to the delegates overview on my site, that way you can get a quick visual overview :)
http://bitsharesblocks.com/delegates
Hmm I updated my version registered as "0.4.11-RC2x64" but it highlights the field as red. I assume this isn't a big issue overall and you likely just coded it to look for a few set strings but is it frowned upon to list the version as verbose as that? Maybe I should change it to just "0.4.11"? Not sure what the best practice is here or if there is one established. Updated client seems to be running smooth though.
-
Hmm I updated my version registered as "0.4.11-RC2x64" but it highlights the field as red. I assume this isn't a big issue overall and you likely just coded it to look for a few set strings but is it frowned upon to list the version as verbose as that? Maybe I should change it to just "0.4.11"? Not sure what the best practice is here or if there is one established. Updated client seems to be running smooth though.
you need to add the version field to your delegate BY HAND!
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
The blockchain does not know what version your run. you need to tell using the 'data' field of your account.
-
Hmm I updated my version registered as "0.4.11-RC2x64" but it highlights the field as red. I assume this isn't a big issue overall and you likely just coded it to look for a few set strings but is it frowned upon to list the version as verbose as that? Maybe I should change it to just "0.4.11"? Not sure what the best practice is here or if there is one established. Updated client seems to be running smooth though.
you need to add the version field to your delegate BY HAND!
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
The blockchain does not know what version your run. you need to tell using the 'data' field of your account.
Ah sorry I didn't explain very well, within my client I see my version info just fine. It's just when viewing my delegate on bitshatesblocks.com that the version field is highlighted red. I'm almost certain that svk just uses some simple logic and turns the field green if it detects the "data" field for "version" as "0.4.10" or "0.4.11" as I see other version entries of "latest" or "0.4.11-RC2" shown in Red as well. I just wasn't sure if when manually updating our client with the version if there was a standard that we were supposed to follow that I missed. As a user defined field I doubt anything in the client uses it other than just for display so I'm probably just nit-picking.
-
dc-delegate
bitsharesx-delegate
updated!
-
The site is flagging 0.4.10, 0.4.11 and 0.4.11-RC in green atm, everything else is in red. I'll improve the logic later today.
-
The site is flagging 0.4.10, 0.4.11 and 0.4.11-RC in green atm, everything else is in red. I'll improve the logic later today.
Ok cool no rush. It was less of a complaint about the site and more just prompted me to wonder if there was standard that was supposed to be followed in case the devs were going to use it somehow for tracking version adoption or for some other purpose.
Thanks.
-
The site is flagging 0.4.10, 0.4.11 and 0.4.11-RC in green atm, everything else is in red. I'll improve the logic later today.
Everything but 0.4.12 should be red at the moment.
-
The site is flagging 0.4.10, 0.4.11 and 0.4.11-RC in green atm, everything else is in red. I'll improve the logic later today.
Everything but 0.4.12 should be red at the moment.
Done!
-
coolspeed
delegate.coolspeed
dac.coolspeed
updated to 0.4.12. Version published.
-
::)
-
::)
Why so sad?
-
x1.sun
x2.sun
updated to 0.4.12
-
Next version will have command: "wallet_publish_version <delegate_name>"
https://github.com/BitShares/bitshares_toolkit/compare/48b5b5224f...985d4acce0
-
Sorry, somehow missed this thread, I have version number published now. Please vote me back. thanks!