βΉοΈ Deletes exactly 2 #XRPL trust lines with very specific IDs that exist solely due to an old bug from 2013, and then does nothing else afterwards.
βΉοΈ Changes the so-called "OfferCreate" #XRPL transactions so that when no funds were really moved while canceling the "Offer," the outcome should not be "success," but rather "killed."
βΉοΈ Transaction cost calculations will be simplified since "fee units" will be replaced withΒ #XRP drops, removing the requirement to convert the results of those "fee units" to XRP first when computing XRP fees.
Nonetheless, I would vote "Nay" for the time being since a ton of servers would get amendment-blocked.
[11/12] β Servers that run on old #rippled code β
Your server must run at least v1.10.0 to avoid being amendment-blocked very soon.
βοΈ Over 200 nodes and 15 validator servers will be impacted βοΈ
[12/12] This should provide you with a high-level summary of the few changes planned to the #XRPL, which will mostly cover and improve performance concerns.
Absolutely eye-opening talk about the intricate nature of things #Evernode, #Hooks, #SmartContracts, and #Codius from the folks who REALLY understand it.
I also really liked how @xrpl365 arranged the "lecture" since he clearly knew what questions needed to be answered. πͺ
I'd also want to mention that @ShortTheFOMO was able to wonderfully clarify his opinions on certain questions I had in the back of my mind.
Seeing Hooks, XRPL, and Evernode in a way that connects to the "simple foundation" that is XRPL helped me understand it. Thanks! βΊοΈ
It was also amusing to me to hear @xrpl365 state out loud what I was thinking about "immutability" while thinking about altering the smart contract as you can on, say, Casper.
Evernode, or more specifically, the Hotpocked dApp, allows you to choose your design:
. . .
After hearing the news of #Ledger willingly integrating a π-extraction mechanism into their FW if opted-in, I decided it was time to review #XUMM + @Tangem
This 𧡠is not sponsored in any way, & all of my praise comes from the bottom of my β€οΈ
[2/13] Browser extensions in and of themselves can easily be the source of #exploits.
So, rather than securing your #browser session, increasing your #privacy, or acting as a warning tool before signing transactions, it may turn out to be your worst enemy.
[3/13] β Attack Vectors β
π§ There are merely two malicious concepts that will be exploited by #hackers to harm you while using #browser extensions:
To learn more, keep on reading and complete the steps. (π Warning: paranoia ahead.) π§΅π
[2/20] β What is the primary goal? β
The basic purpose of an executor address is to claim rewards on your behalf in order to save time, max. compound interest, & reduce unwanted exposure of a cold wallet.
Executors will then use auto. claiming to route rewards to your acc. π
[3/20] β 1β£ Is it safe to assign the task to an executor? β
The executor cannot claim to any address other than the one provided by the user, therefore automatic claiming is secure. πͺ
. . .
Let's look through the website and conduct some research before leaping to conclusions. π§
πΈ Did the #IMF make any comments regarding #DCMA?
πΈ Will this be the end of #XRP?
Let's find out in this π§΅π
[2/16] The Digital Currency Monetary Authority is making moves and expanding its reach through Twitter with its Unicoin network and #UMU, the native Unicoin.
βΉοΈ Who are they and what do they offer?
[3/16] β βΉοΈ β 1β£ #DCMA & #Unicoin β
πΈ Founder working on Unicoin since 2013, yet LinkedIn says 2018
πΈ Just 2 employees
πΈ They refer to themselves as a business, yet there is no registered corporate structure