Jump to content

Multi-Signing, Amendments, Fee Escalation changes published


Recommended Posts

  • Replies 45
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Just today I published the documentation for a bunch of new feature stuff that's coming in rippled 0.31.0. (Right now we're still tracking down the last few bugs in the release candidates, but the fea

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'

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 pap

The first to figure out how to actually host a decentralized smart contract system that uses RCL wins a big jar of cookies.

Quote

scons: done building targets.
root @xagate:/home/rippled# cd build
root @xagate:/home/rippled/build# ./rippled --conf /etc/rippled/rippled.cfg --start
Loading: "/etc/rippled/rippled.cfg"
Watchdog: Launching child 1
2016-May-03 01:30:59 JobQueue:NFO Auto-tuning to 6 validation/transaction/proposal threads
2016-May-03 01:30:59 Application:WRN Validation sequence fields are missing
2016-May-03 01:30:59 Application:NFO Altering table
2016-May-03 01:30:59 Application:NFO Building new indexes
2016-May-03 01:31:13 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported.
2016-May-03 01:31:13 Amendments:DBG Amendment C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490 is supported.
2016-May-03 01:31:13 Amendments:DBG Amendment DA1BD556B42D85EA9C84066D028D355B52416734D3283F85E216EA5DA6DB7E13 is supported.
2016-May-03 01:31:13 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported.
2016-May-03 01:31:13 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported.

 

Edited by Twarden
Link to post
Share on other sites
18 minutes ago, Twarden said:

The first to figure out how to actually host a decentralized smart contract system that uses RCL wins a big jar of cookies.

I think you mean, wins CKE.~jar, which they can either send to their local bakery for cookie deliverables or exchange for BSC.~jarUK or GYT.~tarroES if they'd prefer to eat biscuits or galletas.

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

With rippled 0.31.0 coming out today, we have preliminary dates that we expect the new Amendments to apply:

 

In other words, the countdown is on!

How is it that 0.31.0 is coming out today? It has been available for some time, are the 5 rippled validation servers just now updated to this version?

Link to post
Share on other sites
2 hours ago, jn_r said:

How is it that 0.31.0 is coming out today? It has been available for some time, are the 5 rippled validation servers just now updated to this version?

I guess the code had been pushed to the release branch a while ago, but we only officially released it (release notes, tags, etc) today.

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

I guess the code had been pushed to the release branch a while ago, but we only officially released it (release notes, tags, etc) today.

I see. trying to understand the amendment process here.. So all 5 ripple validators (current situation) must agree for 14 days in a row on an amendment. The timing makes sense more or less (3 May + 14 days = 17 May ~18 May), but the ripple validators - unlike mine or twardens validator - are configured to vote in favour just now only for amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE (New transaction cost management). 

And at 17th May it is planned to configure the ripple validators to also vote in favour for 'Multi-Sig'. 

Edited by jn_r
Link to post
Share on other sites
On 5/3/2016 at 5:56 PM, RafOlP said:

@mDuo13, transaction cost management will be deployed via amendments?

Yes, that's correct. The FeeEscalation amendment, to be precise.

 

On 5/3/2016 at 3:08 AM, jn_r said:

I see. trying to understand the amendment process here.. So all 5 ripple validators (current situation) must agree for 14 days in a row on an amendment. The timing makes sense more or less (3 May + 14 days = 17 May ~18 May), but the ripple validators - unlike mine or twardens validator - are configured to vote in favour just now only for amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE (New transaction cost management). 

And at 17th May it is planned to configure the ripple validators to also vote in favour for 'Multi-Sig'. 

That's exactly correct.

Link to post
Share on other sites
On 5/4/2016 at 4:34 PM, yxxyun said:

When the new fee management deployed, what is the min-fee? still 0.01XRP?

For the time being, 0.01 XRP (10k drops) will be the lowest that the load-adjusted transaction cost will go on our validators.

After seeing how the FeeEscalation fares on the production network for a while, we might adjust that, but I can't make promises there.

Link to post
Share on other sites
On 5/8/2016 at 5:15 AM, yxxyun said:

I found this in code 

std::uint32_t const minFee = 10000;

std::uint32_t const refFee = 10;

fee = std::max(fee, (minFee * loadBase + refFee - 1) / refFee);

This was done in https://github.com/ripple/rippled/commit/b2c9179100328ee700695c9eb7bbf2593c88821c allowed validators to set a hard floor on the fee that they advertised in their validations (note: per the Ripple protocol specs validators can advertise any fee they think appropriate). The code was merged into 0.30.1.

This will likely go away with a future commit, but I can't give you a time frame for when that will be.

Link to post
Share on other sites
  • 2 weeks later...
2 hours ago, yxxyun said:

Apparently not enabled yet ... There is this field "majority" . I can't find a description for this field, but I guess, majority of the validators votes in favor, but waiting to see this being the case 14 days in a row. 515781202 should be a timestamp then, but I can't figure out what kind of timestamp

Quote

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

 

Edited by jn_r
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...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.