0 Members and 1 Guest are viewing this topic.
Quote from: svk on September 04, 2014, 09:23:10 amThe 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.
Quote from: amencon on September 04, 2014, 08:30:03 amHmm 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!Quote from: bytemaster on September 03, 2014, 03:01:30 pmCode: [Select]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.
Code: [Select]wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
wallet_account_update_registration <account_name> <pay_from_account> { "version":"0.4.11" } [delegate_pay_rate]
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