Jayedii 🔺Ⓜ️🕸️
1.4K posts
@jayedii
A Litecoin Chad 🔺Ⓜ️🕸️ $LTC $ERG $AVAX
BREAKING NEWS 🚨 Phil has most likely hit a new level of crazy by potentially hacking into the @aiken_eng account and changing it to Swiper no Swiping lol @rvcas @_KtorZ_ @adamKDean @Quantumplation Idk who runs the account but someone needs to make an announcement.
Algorand protocol development and ecosystem growth are now under one roof. Algorand Foundation and Algorand Technologies ( @Algorand ) have come to a strategic agreement to unify ecosystem operations. This agreement creates a unified powerhouse for blockchain innovation here in the United States and positions Algorand as the chain that enables financial empowerment at scale.
No. 1. None of the reported numbers on the Aiken version reflects the current implementation. E.g. - The transfer simple is currently at [cpu: 68.97M, mem: 193.70K], so about on-par - The mixed many transfer sits at [cpu: 107.93M, mem: 307.89K], well below the Plutarch's implementation - etc... 2. The difference IS about micro-optimisations. We are talking couple of % in the 100M cpu and 100K mem range. So 1% difference is about 0.01% of the overall transaction max budget. Said differently, a difference of 1% roughly translates to 200 lovelaces of execution cost; that's about $0.00005. 3. The size of the Plutarch scripts is 4522 bytes. Aiken's latest scripts weight 2787 bytes. Each byte costs *at least* (if reference inputs, and in the lowest price tier) 15 lovelace. So that's currently a difference 26,025 lovelace. So even if the Aiken version was 130% more costly; it would still be balanced by the script size. For the complete analysis / rationale, please read: github.com/cardano-founda…
Comprehensive benchmarks of Plutarch implementation of programmable tokens against the Aiken implementation (on average the Plutarch implementation is 39.6% more efficient) This benchmark covers real use-case scenarios pulled from actual DeFi transactions from the ledger history. For a practical example, a DEX transaction which processes 16 swap requests when converted to the equivalent transaction on the programmable tokens mini-ledger is 28% more expensive in the Aiken implementation. In every single case, the Plutarch implementation is more efficient. In the largest observed difference, the Aiken implementation consumed 3.33x more CPU and 2.4x more memory than the Plutarch equivalent. The difference here is not micro-optimization, it is an entirely separate class of efficiency. We are not talking about a 5% difference; we are talking about an average difference in efficiency of 39.6% across benchmarks produced from real world use-cases randomly sampled from mainnet DeFi protocols.
I'm not defending racism. I'm defending the right to free speech that people have, no matter who they are or what their views are, good or bad, no matter how they express it. I'm also defending the merit of peoples' work that is separate from their personal views and opinions. I'm also defending their place in the ecosystem because of the merit of their work.
No. 1. None of the reported numbers on the Aiken version reflects the current implementation. E.g. - The transfer simple is currently at [cpu: 68.97M, mem: 193.70K], so about on-par - The mixed many transfer sits at [cpu: 107.93M, mem: 307.89K], well below the Plutarch's implementation - etc... 2. The difference IS about micro-optimisations. We are talking couple of % in the 100M cpu and 100K mem range. So 1% difference is about 0.01% of the overall transaction max budget. Said differently, a difference of 1% roughly translates to 200 lovelaces of execution cost; that's about $0.00005. 3. The size of the Plutarch scripts is 4522 bytes. Aiken's latest scripts weight 2787 bytes. Each byte costs *at least* (if reference inputs, and in the lowest price tier) 15 lovelace. So that's currently a difference 26,025 lovelace. So even if the Aiken version was 130% more costly; it would still be balanced by the script size. For the complete analysis / rationale, please read: github.com/cardano-founda…
No. 1. None of the reported numbers on the Aiken version reflects the current implementation. E.g. - The transfer simple is currently at [cpu: 68.97M, mem: 193.70K], so about on-par - The mixed many transfer sits at [cpu: 107.93M, mem: 307.89K], well below the Plutarch's implementation - etc... 2. The difference IS about micro-optimisations. We are talking couple of % in the 100M cpu and 100K mem range. So 1% difference is about 0.01% of the overall transaction max budget. Said differently, a difference of 1% roughly translates to 200 lovelaces of execution cost; that's about $0.00005. 3. The size of the Plutarch scripts is 4522 bytes. Aiken's latest scripts weight 2787 bytes. Each byte costs *at least* (if reference inputs, and in the lowest price tier) 15 lovelace. So that's currently a difference 26,025 lovelace. So even if the Aiken version was 130% more costly; it would still be balanced by the script size. For the complete analysis / rationale, please read: github.com/cardano-founda…
