Bem-vindo, Xahau! 🇧🇷
https://t.co/1D5AnS4OFv is now available in Brazilian Portuguese, thanks to @andreirosseti.
If you'd like to see the Xahau website and documentation available in your own language, you can help by contributing translations to the official repository: https://t.co/zfdpm2n9Ow
Every contribution helps make Xahau more accessible to users around the world.
@Cryptocrazy589 I was trying to do something similar, but it didn't happen because creating the test data was just too much work.
Your idea of using live data or historical data is really great!
I think the same can be said about the Permissioned Domain/DEX at this point.
I remember there were very strong voices in the community saying this was needed, or pushing for a quick "yes" vote on the Amendment.
However, despite all that pressure to hurry up, I don't think we can really say it's being widely used right now.
XRPL has seen many new features added over the past few years.
However, I don't think we can really say that all of them are actually being used.
Take DID, for example.
Some might argue it's necessary because it will be used in the future. But considering it hasn't been used much even after a year and a half since activation, I think we need to carefully examine whether newly proposed features are truly necessary.
This is also to avoid making XRPL overly complex.
@9oelM The vast majority of users who fall for those kinds of scams probably don't to use one, right?
Teaching someone like that how to use a CLI would clearly just be asking for more trouble like further fraud.
This would work not just for multi-sig but also for RegularKey, but the real issue is whether the wallets people are using actually support these signing methods well enough.
If a wallet doesn't support them and users are forced to switch to one they aren't used to, there's a risk they might get caught in another scam during that transition.
So there's still a potential way to prevent the worst once you have your XRPL account private key leaked due to a mistake.
The XRPL is a completely safe, institutional-grade blockchain, but private key leaks sometimes happen due to users' mismanagement of private keys or ongoing scams on social media.
*note: this approach will only work if you have a bit of time to rescue your account. For example, maybe you have a pending withdrawal from a yield generating protocol on XPRL, or the attacker is not acting as quickly, etc.
Built a quick XRPL POC for exactly this: basically you send out txs to turn your account into multisig and disable the master private key.
Once both land, attacker's tx bounces with tefMASTER_DISABLED. only your 2-of-2 multisig can move funds.
It's a race between you and the attacker but it's one of the things you could try.
https://t.co/CkCrofLyUs
Love seeing new projects launch on the Xahau blockchain and more community members taking part.
Don't be afraid to start building, it's still early, and there's plenty of room for new ideas!
XRPL has seen many new features added over the past few years.
However, I don't think we can really say that all of them are actually being used.
Take DID, for example.
Some might argue it's necessary because it will be used in the future. But considering it hasn't been used much even after a year and a half since activation, I think we need to carefully examine whether newly proposed features are truly necessary.
This is also to avoid making XRPL overly complex.
It's not possible to completely retire or disable an amendment once it has already been enabled. This is basically because we need to support any ledger entries that have already been created.
That being said, from a technical standpoint, it is possible to disable or make certain added transactions unavailable.
In the past, we have disabled amendments that weren't enabled yet, even though the code itself remained. NFToken V1 is a good example of that.
But seeing as pDEX isn't being used much right now, I'm a bit concerned that the Lending feature might end up the same way.
If neither pDEX nor Lending get much traction, then pDomain and Credential probably won't be used either.
And since Lending uses MPTs, we might have to include MPTs in that list as well.
@JonFairbourne But for NFTs, there have been platforms and users using them ever since the amendment was activated.
At the very least, there are still users who need this feature right now.