Jump to content
mDuo13

Multi-Signing, Amendments, Fee Escalation changes published

Recommended Posts

Some extra fields seem to have been added in the mean time..but FeeEscalation not yet "enabled"..

I wonder how it is that there are extra fields now. Is something else enabled?

Quote

rippled@/opt/ripple/bin>./rippled feature
Loading: "/etc/opt/ripple/rippled.cfg"
Connecting to 127.0.0.1:5005
{
   "result" : {
      "features" : {
         "42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE" : {
            "count" : 6,
            "enabled" : false,
            "majority" : 515781202,
            "name" : "FeeEscalation",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 384
         },
         "4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373" : {
            "count" : 1,
            "enabled" : false,
            "name" : "MultiSign",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         },
         "6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC" : {
            "count" : 1,
            "enabled" : false,
            "name" : "TrustSetAuth",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         },
         "C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490" : {
            "count" : 1,
            "enabled" : false,
            "name" : "Tickets",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         },
         "DA1BD556B42D85EA9C84066D028D355B52416734D3283F85E216EA5DA6DB7E13" : {
            "count" : 1,
            "enabled" : false,
            "name" : "SusPay",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         }
      },
      "status" : "success"
   }
}

 

Edited by jn_r

Share this post


Link to post
Share on other sites

Once an amendment gets a majority, it needs to retain that majority for two weeks before it can be enabled. This amendment got a majority at time 515781202 which (warning: rough math on a sheet of paper) works out to 13 days and 8 hours ago. So, as of this writing, there's still a few hours left to go before this amendment is ratified.

P.S.: I'll look at adding a human-readable timestamp in the output.

Share this post


Link to post
Share on other sites
18 minutes ago, nikb said:

Once an amendment gets a majority, it needs to retain that majority for two weeks before it can be enabled. This amendment got a majority at time 515781202 which (warning: rough math on a sheet of paper) works out to 13 days and 8 hours ago. So, as of this writing, there's still a few hours left to go before this amendment is ratified.

P.S.: I'll look at adding a human-readable timestamp in the output.

Do they have to be verified to be part of the majority? Like, could I cobble together 100 computers to screw up the majority? 

Share this post


Link to post
Share on other sites

 

5 minutes ago, Morty said:

Do they have to be verified to be part of the majority? Like, could I cobble together 100 computers to screw up the majority? 

It doesn't work like that, and verified or not doesn't mean much. Let's say you "cobbled together" 100 computers, and setup each as a validator. Does anyone trust you? Unless they do, they'll ignore your votes, just like they'll ignore your validations. :)

Share this post


Link to post
Share on other sites
3 hours ago, nikb said:

Does anyone trust you? Unless they do, they'll ignore your votes, just like they'll ignore your validations. :)

I remember this question has been asked previously but I forget - is it possible to see what other nodes that a given node "trusts"? 

Share this post


Link to post
Share on other sites
1 minute ago, Hodor said:

I remember this question has been asked previously but I forget - is it possible to see what other nodes that a given node "trusts"? 

No.

Share this post


Link to post
Share on other sites

Ok, FeeEscalation is now live :good:

The next to vote for will be MultiSign (according to mduo13), but the validators have not started to vote in favor yet for that one.

Quote

rippled@/home/rippled>rippled feature
Loading: "/etc/opt/ripple/rippled.cfg"
Connecting to 127.0.0.1:5005
{
   "result" : {
      "features" : {
         "42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE" : {
            "enabled" : true,
            "name" : "FeeEscalation",
            "supported" : true,
            "vetoed" : false

         },
         "4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373" : {
            "count" : 1,
            "enabled" : false,
            "name" : "MultiSign",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         },
         "6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC" : {
            "count" : 1,
            "enabled" : false,
            "name" : "TrustSetAuth",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         },
         "C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490" : {
            "count" : 1,
            "enabled" : false,
            "name" : "Tickets",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         },
         "DA1BD556B42D85EA9C84066D028D355B52416734D3283F85E216EA5DA6DB7E13" : {
            "count" : 1,
            "enabled" : false,
            "name" : "SusPay",
            "supported" : true,
            "threshold" : 4,
            "validations" : 6,
            "vetoed" : false,
            "vote" : 64
         }
      },
      "status" : "success"
   }
}


 

Share this post


Link to post
Share on other sites
7 hours ago, Hodor said:

I remember this question has been asked previously but I forget - is it possible to see what other nodes that a given node "trusts"? 

If I remember correctly here is a way to statistically infer validator trust but not with 100% accuracy. It's been a long time since saw this though, I could easily be mistaken. 

Share this post


Link to post
Share on other sites

In case you're curious, FeeEscalation got turned on by (pseudo-)transaction 5B1F1E8E791A9C243DD728680F108FEF1F28F21BA3B202B8F66E7833CA71D3C3 in ledger 21225473. (There's a bug right now where you can't look up pseudo-transactions using the tx command, but transaction_entry works.)

Also, I think we found that the open ledger cost escalation works better when the "fee knobs" aren't forcing the load-based fee to be at least 1000x, which means we're going to be turning the "fee knobs" setting off sooner than expected!

Share this post


Link to post
Share on other sites
4 minutes ago, mDuo13 said:

In case you're curious, FeeEscalation got turned on by (pseudo-)transaction 5B1F1E8E791A9C243DD728680F108FEF1F28F21BA3B202B8F66E7833CA71D3C3 in ledger 21225473. (There's a bug right now where you can't look up pseudo-transactions using the tx command, but transaction_entry works.)

Also, I think we found that the open ledger cost escalation works better when the "fee knobs" aren't forcing the load-based fee to be at least 1000x, which means we're going to be turning the "fee knobs" setting off sooner than expected!

just fee escalation? or multi-signing as well?

Share this post


Link to post
Share on other sites
18 hours ago, kanaas said:

just fee escalation? or multi-signing as well?

Each amendment is separate. The "FeeEscalation" amendment was enabled with the pseudo-transaction that @mDuo13 quoted after support for the amendment reached a majority and maintained it for 2 weeks.

The "MultiSign" amendment will be enabled under a different pseudo-transaction, once it, separately, reaches and maintains a majority for a period of two weeks.

Share this post


Link to post
Share on other sites

I was wondering, is an amendment definite once it is enabled? And will the list of enabled amendments keep on growing or is this list cleaned up at a next rippled release (0.32)?

Share this post


Link to post
Share on other sites
1 hour ago, jn_r said:

I was wondering, is an amendment definite once it is enabled? And will the list of enabled amendments keep on growing or is this list cleaned up at a next rippled release (0.32)?

Once an amendment is enabled it takes an amendment to "undo" it.

The list will, likely, get pruned at some point, but there's no need to prune it just yet.

Share this post


Link to post
Share on other sites
16 minutes ago, nikb said:

Once an amendment is enabled it takes an amendment to "undo" it.

The list will, likely, get pruned at some point, but there's no need to prune it just yet.

Thanks nikb for you answer. I have another question: If 1 or 2 from the validators would crash beyond repair and their DB would have to be rebuilt from scratch, how will they know which amendments are to be enabled?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...