@JoelKatz@RippleXDev@bgarlinghouse I am the member of the community that sadly locked his 50K XRP The NestedSigning ammendment will allow me to regain access to my funds and avoid this from ever happening in the future while making the network even more resilient @WietseWind
I believe in one God,
the Father Almighty,
Maker of heaven and earth,
of all things visible and invisible.
I believe in one Lord Jesus Christ,
the Only Begotten Son of God,
born of the Father before all ages.
God from God,
Light from Light,
true God from true God,
begotten, not made,
consubstantial with the Father;
through Him all things were made.
For us men and for our salvation
He came down from heaven,
and by the Holy Spirit
was incarnate of the Virgin Mary,
and became man.
For our sake He was crucified under Pontius Pilate,
He suffered death and was buried,
and rose again on the third day
in accordance with the Scriptures.
He ascended into heaven
and is seated at the right hand of the Father.
He will come again in glory
to judge the living and the dead,
and His kingdom will have no end.
I believe in the Holy Spirit,
the Lord, the Giver of life,
who proceeds from the Father and the Son,
who with the Father and the Son is adored and glorified,
who has spoken through the prophets.
I believe in one, holy, catholic, and apostolic Church.
I confess one Baptism
for the forgiveness of sins,
and I look forward to the resurrection of the dead
and the life of the world to come.
Amen. 🙏🏼
@JoelKatz@RippleXDev@bgarlinghouse I am the member of the community that sadly locked his 50K XRP The NestedSigning ammendment will allow me to regain access to my funds and avoid this from ever happening in the future while making the network even more resilient @WietseWind
@BrandonBiggs247 God bless you brother in Christ. I kindly request your prayer, I locked $100,000 worth of XRP at the time of purchase. Your prayer would be greatly appreciated, Blessings!
@BrandonBiggs247 God bless you brother in Christ. I kindly request your prayer, I locked $100,000 worth of XRP at the time of purchase. Your prayer would be greatly appreciated, Blessings!
@JoelKatz@RippleXDev@bgarlinghouse I am the member of the community that sadly locked his 50K XRP The NestedSigning ammendment will allow me to regain access to my funds and avoid this from ever happening in the future while making the network even more resilient @WietseWind
Let me make this very clear: Big Banks (think JPMorgan Chase, Bank of America, Wells Fargo, etc.) are lobbying overtime to block Americans from getting higher yields on their savings—while trying to block any rewards or perks from being given to customers.
These banks, and others, pay rock-bottom rates on standard savings (often 0.01%–0.05% APY), even as the Fed pays them 4% or more. This massive spread fuels record profits, with almost none passed back to their customers / everyday depositors.
Today, the banks are desperately targeting crypto/stablecoins, where platforms plan to offer 4–5%+ yields or rewards. The ABA and other lobbyists are spending millions trying to ban or restrict those yields via bills like the Clarity Act, crying “fairness” and using words like "stability"—when it's really about protecting their low-rate monopoly and preventing deposit flight. This is anti-retail, anti-consumer, and straight-up anti-American.
Next time you see a big bank dropping billions on a shiny new Midtown Manhattan HQ, you know exactly where that money comes from: the non-existent interest rate they “pay” you!
Fortunately, the big banks are losing this fight as customers wake up to the games…
@worldlibertyfi
Thanks to the @XahauNetwork team for working on nested signing. Special thanks to @WietseWind and @RichardXRPL.
The XRPL needs more failsafes to account for user error.
I made a costly mistake, but surprisingly the XRPL allowed the transaction. I locked all my $XRP while enabling multi-sig on my wallet. @RippleXDev@Ripple please take a look at what @WietseWind is working on to stop this from happening again.
https://t.co/O90UcnonAU
About three weeks ago I posted an amendment that would resolve a locked-out multi sign setup, causing one of our community members to be locked out of 50k XRP.
If we allow tech to bail on users this way, we're failing the ecosystem (in my opinion). Three weeks later not much has happened. There's a proposal for a different approach, that (imo) doesn't cut it. Why?
There are a few approaches to fixing XRPL accounts that get stuck because their signers independently changed their own key setup:
- Ban invalid signer configs at transaction time. Doesn't work. The lockout happens across multiple accounts over time, each transaction was valid when submitted. You can't prevent it without restricting what people do with their own keys.
- (Counterproposal by Ripple staff) Let a disabled master key still work as a signer on someone else's account. Gets the job done for already-stuck accounts but breaks a core assumption: disabled means disabled. If you turned off your master key because it leaked, you don't want it suddenly usable again in some other context.
- (Our approach) Nested multi-sign. Walk the signer-of-signer chain recursively, detect cycles, relax quorum where needed. Recovers stuck accounts without changing what "disabled" means. DoS concerns are real but solvable with a global signature verification cap per transaction (Batch already allows 288 sig verifications today, nested multi-sign caps at 64).
I strongly believe option 3 is the right path. It's the only one that actually fixes things without weakening security guarantees.
PR: https://t.co/5yXk4z1XIk
XLS: https://t.co/45K9CoaC7L
⏳
@WietseWind I'll never forget what you've done, people like you make this world a better one. The level of kindness and compassion you have shown is truly remarkable and worthy of admiration. You truly are a remarkable person @WietseWind.