Angehefteter Tweet
Settee
534 posts

Settee
@SetteeCh
Founder/CEO @PennysiaLabs, CS alumni @mahidolinter
Bangkok, Thailand Beigetreten Şubat 2023
1.1K Folgt215 Follower
Settee retweetet

Thai Bitcoiners translate Broken Money by @LynAldenContact
Great work @piriya and those that helped make this possible.



English
Settee retweetet
Settee retweetet

Made some updates.
This has been my work for the past 3 weeks. Although selling point is the mechanism, architecture and overall code quality affect DevX and scalability.
Pennysia@PennysiaLabs
We've successfully made the 1st full-feature core smart contract deployment on the Testnets. docs.pennysia.com/resources/depl…
English

I always wanted to play with Bitchat since last year🥲 The improvement was speedy!
Documenting Saylor@saylordocs
🇺🇸 Billionaire Jack Dorsey app Bitchat let users send Bitcoin without internet. Wild!
English
Settee retweetet
Settee retweetet
Settee retweetet

new collab from @paradigm and @OpenAI:
evmbench is a benchmark and agent harness for exploiting smart contract bugs
a few months ago, the best models found <20% of critical, fund-draining @Code4rena bugs in our benchmark. today they find > 70%
OpenAI@OpenAI
Introducing EVMbench—a new benchmark that measures how well AI agents can detect, exploit, and patch high-severity smart contract vulnerabilities. openai.com/index/introduc…
English

คุยกับน้องคนไทยที่ทำ defi บน Sonic @SrpSutach
Pennysia เป็น Project ของคนไทยเลย ทีมเราเริ่มตอนช่วง 2019-2020 เริ่ม research เเละ build มาเรื่อยๆ โดยทีมงานได้เน้นทำ AMM protocol พวก Dex พบว่าตามหลัก LP ได้ไม่ดีเท่าที่ควร ทรมงานเลยทํา DEXs ที่มี Prediction Market ที่คนสามารถ Bet ว่า Bulliish or Bearish ขณะที่กําลังวาง LP ซึ่งผลตอบเเทนมันดีกว่า Hold LP ปกติ ซึ่งแปลว่าตัวนี้มีต่อ prediction market ไปด้วยซึ่งแหวกแนวดีครับ
โดยการวาง LP ที่ Pennysia ได้ revenue 4 ทาง
1.) LP
2.) AAVE
3.) Prediction Market
4.) Protocol revenue return back to LP
ไทย
Settee retweetet
Settee retweetet

We've successfully made the 1st full-feature core smart contract deployment on the Testnets.
docs.pennysia.com/resources/depl…
English

RT @VitalikButerin: Recently I have been starting to worry about the state of prediction markets, in their current form. They have achieved…
English
Settee retweetet
Settee retweetet

Have been following reactions to what I said about L2s about 1.5 days ago.
One important thing that I believe is: "make yet another EVM chain and add an optimistic bridge to Ethereum with a 1 week delay" is to infra what forking Compound is to governance - something we've done far too much for far too long, because we got comfortable, and which has sapped our imagination and put us in a dead end.
If you make an EVM chain *without* an optimistic bridge to Ethereum (aka an alt L1), that's even worse. We don't friggin need more copypasta EVM chains, and we definitely don't need even more L1s. L1 is scaling and is going to bring lots of EVM blockspace - not infinite (AIs in particular will need both more blockspace and lower latency than even a greatly scaled L1 can offer), but lots.
Build something that brings something new to the table. I gave a few examples: privacy, app-specific efficiency, ultra-low latency, but my list is surely very incomplete.
A second important thing that I believe is: regarding "connection to Ethereum", vibes need to match substance.
I personally am a fan of many of the things that can be called "app chains". For example I think there's a large chance that the optimal architecture for prediction markets is something like: the market gets issued and resolved on L1, user accounts are on L1, but trading happens on some based rollup or other L2-like system, where the execution reads the L1 to verify signatures and markets. I like architectures where deep connection to L1 is first-class, and not an afterthought ("we're pretty much a separate chain, but oh yeah, we have a bridge, and ok fine let's put 1-2 devs to get it to stage 1 so the l2beat people will put a green checkmark on it so vitalik likes us").
The other extreme of "app chain", eg. the version where you convince some government registry, or social media platform, or gaming thing, to start putting merkle roots of its database, with STARKs that prove every update was authorized and signed and executed according to a pre-committed algorithm, onchain, is also reasonable - this is what makes the most sense to me in terms of "institutional L2s". It's obviously not Ethereum, not credibly neutral and not trustless - the operator can always just choose to say "we're switching to a different version with different rules now". But it would enable verifiable algorithmic transparency, a property that many of us would love to see in government, social media algorithms or wherever else, and it may enable economic activity that would otherwise not be possible.
I think if you're the first thing, it's valid and great to call yourself an Ethereum application - it can't survive without Ethereum even technologically, it maximizes interoperability and composability with other Ethereum applications.
If you're the second thing, then you're not Ethereum, but you are (i) bringing humanity more algorithmic transparency and trust minimization, so you're pursuing a similar vision, and (ii) depending on details probably synergistic with Ethereum. So you should just say those things directly!
Basically:
1. Do something that brings something actually new to the table.
2. Vibes should match substance - the degree of connection to Ethereum in your public image should reflect the degree of connection to Ethereum that your thing has in reality.
English

Fundamentally @flyingtulip_ raise strategy is simply: deposit money to the bank without earning interest. Instead, the protocol take your deposit interest paid by the bank and get you token allocation in return.
You then have 2 options: withdraw the deposit OR claim the allocated token.
- If withdraw, your allocated token portions are permanently burned. This does not affect the price, but it increase token scarcity.
- If claim, your deposit is taken as liquidity to back the token price.
The systemic risks are tied to the DeFi banks they delegate these deposits to (eg. @aave)
The limitation I see is that since the protocol only earns from interest(around ~3-5%), it requires a large amount of deposit to make the flywheel works.
English










