@StefanBurnsGeo This appears to be a rhythm. My intuition: earth's magnetic frequency is readjusting now that @CERN is undergoing *repairs* and we seem to have resccessed human control of lava tubes nuclear fusion technology time travel and star gates.
@AngelA1453639@StreamerBatch Still a soul, one of God's children. I think something will wake him up... but from what I am gathering, it appears to be an act.
XLS-0078 Subscriptions are now available on the custom node and ready to test.
https://t.co/Aq8ztwrWbv
This is the amendment we curated at the first XRPL Core Developer Bootcamp. Kris Dangerfield (@krisdangerfield) wrote the original spec, Denis (@angell_denis) opened the first rippled PR and I have ported it onto a standalone node so it can be tested before a new PR is submitted.
A subscription is a native standing pull. The subscriber authorises a payee to claim up to an Amount, at most once per Frequency, in the same asset for the life of the object, with an optional Expiration. The payee claims. The subscriber can update the cap. Either side can cancel. Frequency, destination and start time stay fixed after Set, so the original terms cannot be quietly rewritten.
The build is experimental and custom-node only. Type codes have been remapped for this fork to align with the XRPLD development branch. The sandbox covers Set, Claim, Update and Cancel on both an XRP path and an RLUSD path, with the spec beside the live result.
If you care about this feature, the useful thing now is to test it by creating one, claim too early, claim after expiry, try a payee update, and let us know if anything feels wrong.
Test, Share Results and join the discussion👇
XLS-0078-Subscriptions ~ https://t.co/zaUpYuvwLy
#XRPL #XLS #Subscriptions