Lost Art

Powering @MyWeb3me | @XRPSoCal 2026 | $XRP Gold & Silver Coin | Fostering Blockchain adoption through Art, Tech, & Entertainment.

[Lost Art @OCLostArt]

Who's ready⁉️ #XRPSoCal2026

[Hamsa @JoshuaHamsa]

The best of $XRP in Southern California.

[Lost Art @OCLostArt]

@JoshuaHamsa Lets go‼️

[Lost Art @OCLostArt]

The best of $XRP in Southern California.

👉 @XRPSoCal

[Arsyde @Arsyde_]

The best of $XRP in Southern California.

👉 @XRPSoCal

[Lost Art @OCLostArt]

Nothing major but a meaningful change.

[XRP Ledger Operations @XRPLOperations]

XRP Ledger 3.2.0 is coming soon!

The core software powering the XRPL is changing its name from rippled to xrpld.

This transition will require some updates for infrastructure operators. We're preparing a detailed playbook to help guide you through the upgrade process.

[Lost Art @OCLostArt]

@j00sko We hope to see you on there soon. It would definitely be a great addition and improvement.

[Lost Art @OCLostArt]

@FlareDevHub On the contrary, thanks for doing what you do. ✊️

[Lost Art @OCLostArt]

We've updated our UNL to include @FlareNetworks XRP Validator. We believe they bring the experience, expertise, and integrity needed to contribute to the ledger’s long-term health and performance.

You can review our changes here:: 👇

https://t.co/sCXjdi2C5v

[Lost Art @OCLostArt]

🚧 Scheduled Maintenance Notice: We are restarting our validator's rippled service. An update will follow within the hour or upon completion.

[Lost Art @OCLostArt]

Our validator is back online. You can view its status on @xrpscan. 👇

https://t.co/fOg1grOAjp

[Lost Art @OCLostArt]

🚧 Scheduled Maintenance Notice: We are restarting our validator's rippled service. An update will follow within the hour or upon completion.

[Lost Art @OCLostArt]

We finally created a page for our yearly $XRP event in Southern California. It's our fifth year in a row. If you're in the area, have attended, or plan to attend, give it a follow. @XRPSoCal

[Lost Art @OCLostArt]

@ResilientLuna 🫡🖤

[Lost Art @OCLostArt]

We finally created a page for our yearly $XRP event in Southern California. It's our fifth year in a row. If you're in the area, have attended, or plan to attend, give it a follow. @XRPSoCal

[Lost Art @OCLostArt]

Right now, every XRPL amendment waits a fixed 14 day period after reaching 80% validator approval before going live. While many of us have become accustomed to this waiting period, it creates a major problem when zero day attacks or critical bugs are discovered.

The lack of any mechanism to quickly address network security, stability, or integrity vulnerabilities has motivated us to propose a new amendment, Dynamic Activation.

This proposal introduces an optional activationTag (0–4) added to each amendment, allowing amendment authors to choose faster, risk-appropriate activation windows:

4 = 14 days (default)
3 = 10 days
2 = 3 days
1 = 24 hours
0 = Immediate (for active exploits)

By making this field optional and defaulting to 4, the amendment remains fully backward compatible while preserving the existing XRP Ledger standards. An amendment should have an activationTag of 4 unless it is addressing a vulnerability or active attack. If an amendment is given an activationTag that's too aggressive with no justification, validators can simply vote no.

This change could drastically improve rapid response times by helping to offset the delays from bug fix development, UNL inactivity, testing, and the standard two week activation period when addressing critical network wide vulnerabilities and zero day attacks.

We currently have no way to address active attacks. We need one.

Help us improve the XRP Ledger by joining the discussion. Link in the first comment.👇

[Lost Art @OCLostArt]

@XRPCRYPTOFRESH @Arsyde_ $XRP

[FRESH ◉ @XRPCRYPTOFRESH]

@OCLostArt @Arsyde_

[Lost Art @OCLostArt]

What's trending with $XRP?

https://t.co/sJZzVbfNDt

[Arsyde @Arsyde_]

What if I said that the one and only @JoelKatz is the one who'll be drafting the code? Would you care more?

Just a what if, not confirming or denying anything. 🤓

[Lost Art @OCLostArt]

@ShortTheFOMO It was. It's always a good time chatting with you.

[Lost Art @OCLostArt]

Right now, every XRPL amendment waits a fixed 14 day period after reaching 80% validator approval before going live. While many of us have become accustomed to this waiting period, it creates a major problem when zero day attacks or critical bugs are discovered.

The lack of any mechanism to quickly address network security, stability, or integrity vulnerabilities has motivated us to propose a new amendment, Dynamic Activation.

This proposal introduces an optional activationTag (0–4) added to each amendment, allowing amendment authors to choose faster, risk-appropriate activation windows:

4 = 14 days (default)
3 = 10 days
2 = 3 days
1 = 24 hours
0 = Immediate (for active exploits)

By making this field optional and defaulting to 4, the amendment remains fully backward compatible while preserving the existing XRP Ledger standards. An amendment should have an activationTag of 4 unless it is addressing a vulnerability or active attack. If an amendment is given an activationTag that's too aggressive with no justification, validators can simply vote no.

This change could drastically improve rapid response times by helping to offset the delays from bug fix development, UNL inactivity, testing, and the standard two week activation period when addressing critical network wide vulnerabilities and zero day attacks.

We currently have no way to address active attacks. We need one.

Help us improve the XRP Ledger by joining the discussion. Link in the first comment.👇

[Lost Art @OCLostArt]

Here's the GitHub discussion.

https://t.co/WDTGINy1Tw