Quantumplation | Pi Lanningham

13.5K posts

Quantumplation | Pi Lanningham

Quantumplation | Pi Lanningham

@Quantumplation

CTO Sundae Labs | https://t.co/9PNVVduxQs Trying to be less active on Twitter drep158mfwdv7lvqzg0yrdxwhsmkq5406nmvw4yvjyyfcawlwus2eylt

Katılım Haziran 2008
274 Takip Edilen8.7K Takipçiler
Sabitlenmiş Tweet
Quantumplation | Pi Lanningham
Quantumplation | Pi Lanningham@Quantumplation·
Below you will find my write-up as an independent after action report for the issue impacting Cardano late last week, along with things I learned, why I was impressed, and what I think we can do better at in the future. I try to strike the balance between confronting the seriousness of the issue, while defusing most of the over-stated positions from talking heads on Twitter. This is an adult conversation, not whatever the children are engaging in on Twitter this week. I don't think it's productive to get into debates of what constitutes "downtime" or not; Instead, I tried to equip you with a framework where you, dear reader, can think about these things for yourself, and decide what you want to call it. I just ask that you make that decision for yourself, or allow your audience to do so, rather than parroting some pre-decided talking points. More informed discussion leads to a higher quality industry overall. 314pool.com/post/cardano-p…
English
63
157
664
88.5K
Quantumplation | Pi Lanningham
Quantumplation | Pi Lanningham@Quantumplation·
This coming Wednesday I'll be doing some live-coding. Currently the plan is to talk about (and show off) how Sundae Labs is leveraging AI to accelerate development, without giving up the commitment to quality or craftsmanship that has made us successful. I'm hoping to co-stream through the @pragma_org Discord, and the official @SundaeSwap Twitter account, I hope to see you there!
PRAGMA@pragma_org

We’re doing a pop-up live coding session next week with Pi Lanningham of SundaeSwap Labs👀 Come hang out, watch real-time development, ask questions and see what the team is working on. 🗓️May 27 🕐1 PM EST Join the Pragma Discord to follow along, link at pragma.io

English
2
13
78
4.4K
Quantumplation | Pi Lanningham
@TheC_Crypto I don't think we need a common policy; I think it's helpful when a drep publishes *their* policy, and delegators can take that into account when delegating.
English
1
0
0
34
The C 🇦🇺
The C 🇦🇺@TheC_Crypto·
@Quantumplation Thanks for the reply Pi 🍻 I think it would be pretty helpful if dreps had agreed upon guidelines about how to determine whether or not they have a conflict of interest. It’s definitely something worthy of a public discussion.
English
1
0
0
32
Quantumplation | Pi Lanningham
I am still in the process of voting, but I have cast votes on 3 of IO's proposals. I have voted YES on the Cardano Upgrades and the Consensus Initiative. I have no ongoing conflict of interest on these proposals, and believe these are essential upgrades for Cardano. I do hope to see a stronger go-to-market / business development plan from the Consensus team, as just building the technology is insufficient, but this wasn't a big enough problem to challenge the proposal, in my opinion. I have voted ABSTAIN on the Blockfrost proposal, though I think it is a good one, because I have discussed with @stakenuts in the past the possibility of being a third party vendor to assist with Project Cayley. While nothing is signed, the possibility that I might receive funds requires me to abstain. I do intend to vote on a majority of the rest, but my integrity requires that I consider them carefully, and drafting well thought out justifications for my vote on top of all my other responsibilities is challenging.😅 You can find longer form jusitifications for my votes on my blog, 314pool.com
English
8
9
145
3.3K
Quantumplation | Pi Lanningham
IMO there's a big difference between being a potential contractor on the work, and receiving some pocket change for a completely unrelated project you support that happens to share a founder. I personally did not feel Nav's "conflict of interest" call out was appropriate or relevant.
English
1
0
2
129
The C 🇦🇺
The C 🇦🇺@TheC_Crypto·
@Quantumplation Appreciate the conflict of interest disclosure. This was exactly what Nav was talking about. It’s ok to support IOG and offer criticism at the same time. Especially looking forward to IOG’s leios proposal receiving funding 🍻
English
1
0
2
219
Blink Labs
Blink Labs@blinklabs_io·
I asked my German friend if he knew the square root of 81. He said “No”.
English
14
1
43
1.7K
Quantumplation | Pi Lanningham
@jonahkoch @stakenuts @_KtorZ_ I'm saying that jumping straight to the Treasury proposal is making it worse. Even if people aren't engaging, proposers should still be at least attempting to get feedback on proposals before submission.
English
2
0
1
46
KtorZ
KtorZ@_KtorZ_·
It's so frustrating the only governance options for withdrawals are "yes" or "no" (abstain is just that in different proportions). What if DReps could propose a counter budget, and vote yes up-to a certain amount? This way we can encapsulate more nuances.
English
14
6
54
2.7K
🪏 Jonah Koch
🪏 Jonah Koch@jonahkoch·
@stakenuts @Quantumplation @_KtorZ_ Exactly this! Zero incentive to participate except loss of certificate due to inactivity, no one feels obligated to participate when it’s off the L1 Only have to look at the participation in the Ekklesia discovery pre-voting process to understand this. < 5 comments is normal
English
2
0
0
58
Quantumplation | Pi Lanningham
@sandstonepool x.com/Quantumplation… Here was the post :) I'd be happy to do one more review, not for the bounty, just for fun, once you think it's "really truly ready"
Quantumplation | Pi Lanningham@Quantumplation

Open challenge to anyone: Vibe-code an alternative Cardano node from scratch in any language except Haskell (could probably allow haskell as well, but there's too much risk that it's just a straight fork). Vibe-coded will mean that: 1) the entire git history is visible from the start of the project 2) 90% of commits include their model and prompt in the commit message, with a "Coauthored by" tag-line from the model, such as what Claude code sometimes attaches 3) if it is written in the language of an existing alternative node effort (rust, go, typescript, C++, C#, etc.) then the MOSS and JPlag scores indicate low structural similarity 4) the above two are subject to reasonable third party remediation Deliver a spec-compliant block producing node ready for main net any time before Amaru or Dingo claim to have done this, or the next year, whichever is later. This means it supports all node-to-node miniprotocols and all node-to-client miniprotocols implemented by the haskell node at the time you make the claim, matches or beats the Haskell node in average memory usage across 10 days, agrees on tip selection to within a generous 2160 slots for the entirety of that 10 days, can recover without human intervention from a power-loss event at any time, and agrees with the Haskell node on all block, validity, chain-tip selection behavior. Give me a 1 month grace period in case I'm busy with other obligations, before I start testing your node. Then, from the time I start testing, give me 5 days. If, in those 5 days, I *am* able to: 1) get your node running and sync from either a recent mainnet mithril snapshot or genesis up to tip and 2) produce a valid block accepted by other nodes on preview or preprod 3) Execute the node to client blockfetch and txsubmission miniprotocols 4) get your node running in a private testnet including 2 other haskell nodes and I *cannot* either: 1) find a transaction for which your node and the haskell node disagree on the validity, or 2) find a block for which your node and the haskell node disagree on the validity, or 3) find a sequence of blocks produced by the devnet for which your node disagrees with the haskell node on the correct consensus tip I will personally pay you $5000 in USDCx or USDM, and vehemently campaign alongside you for retroactive funding from the treasury at the same market rates being proposed by any of the current funding proposals. I would offer more, but I've been making below market rate for my skills for 5 years in an effort to survive in this ecosystem, so I can't actually afford much more myself.

English
1
0
2
126
SANDSTONE
SANDSTONE@sandstonepool·
Thanks for the review PI! To be fair, I wasn't clear on the acceptance criteria and probably missed wherever that post is. Even so, appreciate the assessment. Node v1.7.0 has a substantial amount of additional integration tests in place now which closed a lot of the gaps you found. I'll continue my agentic engineering experiment alive until it gets to parity all the same (obviously without resubmitting as per your rules). All the best! -Sandstone
English
1
0
4
103
Quantumplation | Pi Lanningham
I investigated my first official submission for the vibe-node bounty I issued. (Technically, someone else submitted earlier, but I didn't see the message until much later because of Twitter message requests, and I had trouble running the node, so I have given them a second chance to submit once they correct the issues.) My verdict: Dugite has failed to be a compliant node, and is disqualified from all future submissions. If a single node operator were running this node, it could be indefinitely prevented from producing blocks. If a significant minority of block producers were running this node, it could cause significant long-lived forks, similar to the pig-chain fork from last year. If a plurality of block producers were running this node, the plurality of stake would allow spending of *any* funds from any plain VKey wallet by anyone. My full writeup is here: 314pool.com/post/dugite-bo… In total I spent about 8 hours identifying the bug and drafting an exploit for it. At the end of the bounty program (if someone claims the bounty, or the bounty expires), I will publish the scripts I used to reproduce all issues found on all nodes. It wasn't a requirement to apply for my bounty, but if @sandstonepool or anyone else would like to compensate me for my time, you can send something to the ADA Handle $pi
SANDSTONE@sandstonepool

@Quantumplation Let's play! Consider this our official submission: michaeljfazio.github.io/dugite/introdu…

English
5
4
51
4.2K
$cerkoryn | dRep
$cerkoryn | dRep@Cerkoryn·
I've been working on an idea that would allow market makers on Cardano to place/update orders at ultrafast speeds at no cost using regular HTTP transport mechanisms. Only settlement (red box) needs to be on chain. But it needs a light-node smart wallet, ideally in the browser:
$cerkoryn | dRep tweet media
English
4
6
32
1.7K
Quantumplation | Pi Lanningham
No, no API or HTTP needed. Pay funds into a contract from a cold wallet; contract allows you to spend provided it is exchanging X for Y at exchange rate Z, where Z is signed by hot key K. Your local market making agent monitors the price, and when it hits price K, you sign the redeemer, build the transaction, and submit it, through your local tx submission node.
English
1
0
1
264
Quantumplation | Pi Lanningham
no; doing this without any intermediaries is orthogonal; The system that Phil and I are describing works with or without a local tx submission endpoint; The "personal oracle UTxO" isn't solving the local tx submission / intermediary issue, the local light wallet does. If you have a local light wallet, then you can use a signed redeemer to update your order and submit the execution without an intermediary.
English
1
0
2
69
Quantumplation | Pi Lanningham
To clarify: if you want to remove an intermediary for tx submission, you'll need a light wallet for that regardless. If you want to remove the need for batchers (which I think is a misdiagnosis of the problem in the first place, but I digress) you need to design a protocol that allows direct execution. None of these rely on your "personal oracle" utxo, and that can entirely be replaced by a signed redeemer, maybe with a nullifier tree or nonce in your protocol if you want to avoid replay risks
English
1
0
1
71