Delegates can now Publish their Version

[amencon]

Updated delegate alecmenconi with version: 0.4.10.

Will look at updating to 0.4.11 tonight.

[testz]

Updated.

[GaltReport]

Updated:

delegate1-galt
delegate1.john-galt

with current 4.10 version.

[emski]

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 shows 0.4.10 in the "info" command output. However it is referenced by Bytemaster as 0.4.11 .

[muse-umum]

Updated.

Why not check whether the input version matches the one got by 'info' command? It can help avoid faking input or typo.

[emski]

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.

Code Select Expand

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 ).

[spartako]

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.

Code Select Expand

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" } ?

[bytemaster]

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.

Code Select Expand

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.   

[emski]

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.

Code Select Expand

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) ?

[spartako]

Active delegates spartako,spartako1,spartako2 updated:

Code Select Expand


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) >>>


[gyhy]

updated：
dnsdac
w.dnsdac

[Riverhead]

I like it. Updated.

[bytemaster]

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.

Code Select Expand

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.