πΈ 11.December.2023 β Register your addresses
Closes 6:00PM Monday AEDT
Closes 2:00AM Monday EST
β’ Meantime β "Import" onto Xahau and set the correct Trustline
πΈ 18.December.2023 β Targeted Launch
πΈ After Launch β Claim the Evers
[4/20] β 2β£ Basic Overview β Why?
What a struggle, you may say, but the devil is in the details.
They must airdrop on another blockchain based on an XRPL snapshot, screen out people who are unable or unwilling to participate, and match the specific qualifying token numbers.
[5/20] β 1β£ Fundamentals β Regular Key
On XRPL, an account's "regular key" may be viewed as a separate but empowered address with the authority to operate your main account on its behalf.
This is usually the case if you like to have this:
πΈ Deputy Account
πΈ Backup Account
[6/20] β 2β£ Fundamentals β Import
πΈ XUMM β Full Access
One way of importing an XRPL-Account into XUMM is to import the keys or seeds alongside the public address, which will convert your wallet into a "Hot-Wallet."
β Keys should not be migrated from one wallet to another
[7/20] β 3β£ Fundamentals β Import
πΈ XUMM β Read Only
By doing so, you just import the public address of your cold wallet and thereby advise XUMM that it exists and that you wish to see balances or kick off transactions without signing them.
Because the keys are always stored on the card, you may import the public address in read-only mode or safely add your Tangem card in full access mode.
β No security concerns
[9/20] β 5β£ Fundamentals β Import
πΈ XahauL β r-address
This specific "import" of your XRPL account using a yet-to-be introduced tool will assist you in initially setting up your account on XahauL.
@XrplServices has already summed it up precisely π
Have you ever wondered why your signed claim TX is never sent to the XRPL?
This is because it is a XUMM-specific "pseudo-TX-type" that responds with:
β’ Signed by?
β’ Valid signature?
β’ Multi-Signature Wallet?
[11/20] β 1β£ Considerations β
Before we begin the tutorial, a few last words.
We're about to temporarily give another account the authority to sign TXs on our behalf.
If this account was never linked to your cold-wallet, the linking may undermine your privacy or security.
[12/20] β 2β£ Considerations β
We will never migrate or leak keys, instead exposing our cold wallet to a second deputy-account, the XUMM mobile wallet, which is only ever not a hot-wallet when linked with a XUMM branded @Tangem card.
If you're unsure, ask questions! π
[13/20] β 1β£ Tutorial β
πΈ Wallet Preparation (Import)
[14/20] β 2β£ Tutorial β
πΈ Regular Key Configuration
[15/20] β 3β£ Tutorial β
πΈ Evernode Address Registration (XUMM)
[16/20] β Optional Ideas β
Depending on your paranoia, you may even move away your XRP from your cold wallet before continuing the registration w/ an empty wallet.
In this case, you might not even need the extra security of a Tangem card account and just use your hot-wallet.
[17/20] β What's Next? β
With our claim tickets in hand, we are now waiting for @XRPLLabs to launch the "import" tool that will allow us to kickstart our trip on the @XahauNetwork.
After that, we just add a trustline to rEvernodee8dJLaFsujS6q1EiXvZYmHXr8 on the XahauL.
[18/20] β Summary β
πΈ To claim with XUMM, use a regular key setup
πΈ Donβt import/migrate secrets in full access
πΈ XUMM is safe in and of itself, yet still a hot-wallet
πΈ Use a Tangem-card for your regular-key account
πΈ The regular key method doesn't leak keys
[19/20] β Krippenreiter β
I write about DLT and crypto, but primarily about XRP and the XRPL-ecosystem. π₯
If this interests you and you want to learn more, please follow me here:
@krippenreiter
The issue is an unexpected crash that happens when calling a particular method via an API that now returnsΒ a different result than it did previously after changing the API to v2 & unifying the return formats.
[3/9] β 1β£ Release Candidates β
πΈ Software Release Management
There are versions known as "release candidates" in addition to beta versions, which are made available for developers to try out the most recent version.
[1/π§΅] A new major breaking change is on its way to the XRPL ecosystem in the shape of yet another rippled version update.
If all goes as planned, this new version will be available to all node operators by November 13, 2023
Let me introduce you to rippled v2.0.0 π
[2/16] β High-Level Overview β
Don't be put off by the lingo. I promise to go over everything and simplify it for you later.
Here is what's new:
πΈ New API version (v2)
πΈ TPS performance enhancements
πΈ 4 new amendments
πΈ New RPC (method)
πΈ Several bug fixes and refactoring
[3/16] β Software Versioning β
In software development, changes are released in a particular format.
This structure specifies the scale & significance of a change that will be made to an update.
For V2, this implies "major breaking change" owing to a newly proposed API version
I tried to get everything down as accurately as possible, although some of what I wrote may have been misunderstood by me while I listened to the guests speak.
Please pardon any errors, as I welcome you to correct me in the comment section below.
[3/29] β 1β£ Why do we need AMMs? β
β’ We want to be able to buy and sell assets whenever we want, which is why Market Makers are so important
β’ Liquidity will be added, and new usecases will be available on the XRPL
[1/π§΅] No one votes in favor of the XRPL-AMM feature. π€¨
It's been about a month since I last discussed some of the probable reasons behind this.
Let us take another look at what happened in the meantime and how far we have come. π
[2/12] β 1β£st Consideration β
πΈ Network State
100% of all currentΒ UNL-validators have upgraded to v1.12.0, meaning that the XRPL has been sufficiently updated to not halt as a safeguard if an amendment is put into effect.
Furthermore, >54% of all nodes are up to date. π₯
[3/12] β 2β£nd Consideration β
πΈ Amendment-Block
Assuming a 1.12.0-specific amendment is put into effect (like AMM) on the public XRPL, how many nodes will not see the light of day?