TradeLayer (@TradeLayer) header
TradeLayer (@TradeLayer) profile picture

The only trading infra. decentralized enough for agents to rely on. Plug UTXO into Op_Return on BTC, LTC Run your own perps sequencer, 0.5/-0.25 bps fees.

Chile
Joined June 2018
Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)Photo by TradeLayer (@TradeLayer)
TradeLayer retweeted
Only eight lives left .
Readers added context they thought people might want to know
This is obvious AI slop. Cats cannot walk on power lines. Also, note that the cat suddenly has no tail after it survives an electric shock that should have blown it apart, then stands stunned, looking into the camera with its hair sticking out like a Loony Tunes cartoon. merriam-webster.com/dictionary/gul…
480
1,143
102
12,658
789,237
Tradwives have changed
163
90
135
3,095
728,037
launching.jpg
1
3
298
Got a 3-4 week dev roadmap to get Bitcoin in the protocol. Probably a 1000-2000 to 1 staking ratio of tlBTC for the oracle/profit relayer pools to rBTC in DLCs, very nice capital efficiency. George Costanza DeFi Switch level genious. Today I throughput/track bugs. Tomorrow...
1
2
3
334
TradeLayer retweeted
EAST Blue is scaling $BTC for consumer apps and everyday use, designed for mass adoption. Our goal: Making Bitcoin cheaper, faster, and better to bring 1 billion people into the Bitcoin ecosystem. Buckle Up. 🪂
685
15,101
327
15,093
178,255
Testing channel trades successfully, we put in a Mario coin-sounding chime when the trades go through, never felt so satisfying to hear.
1
1
3
578
zerosync.org Right now I can take this + merkle proofs, put a verifier in consensus for a token layer, and make BTC swap for assets on Litecoin. If we had Scrypt proofing we could make ZeroSync for LTC and DOGE and it'd enable 2-way zk rollup trading and bridging.
1
5
418
"What now?" "Now... the hard part begins"
1
278
This is a smarter design than the channel settlement we had before, which had some game theory edge cases. The larger OP_Return space of 83 bytes means I can fit in a txid and nix a trade. Ordinals also open the door to batching a lot of trades into one settlement, just slow.
1
2
3
559
As stated before, if you want to go banoodles in an Ordinals version of this, still 2 tx, but could be slightly more efficient than publishing 3 tx. Anyway you can chain these. So you do a trade, you do a settlement tx referring back to the first trade, neither are published, then you do another "trade" by settling, so, you have an init position and then you settle referring to that tx, you sign a new tx for a new trade, you sign a new settle tx referring to that, etc. If I had say 200 bytes of space in OP_Return that would be relayed (an easy soft fork, change a single line of code, change the int) then I could refer to *two* txids and you'd be able to chain infinite amount of unpublished tx and punt on their expiration times. Nonetheless this is a great improvement in the L2 architecture vs. the 2019 draft, where the L2 aspect was sorta subject to experimentation. At least here you can open a position and keep chaining a series of settlement tx to keep it alive and unpublished indefinitely. You need a watchtower service to challenge any fraud/welch attempts, could bond a Tendermint or other L3 to serve that function or just run a forever.js script on a VPS yourself. You 👏 can👏keep👏an👏L2👏trade👏open👏indefinitely! I will add ordinal support later so you can do this for a bunch of different positions with one dealer channel or with a bunch of open-settleClose, open-settleClose trades and glom all those txids to be nuetralized from the various settlement tx, into one settlement tx. The JSONs revealed in the MAST still are chain bloat though. Which brings me to the L3 idea which is the perfection of TradeLayer, which I've been narrowing in on since late 2021, which is a zk rollup that does this more efficiently. Proof of co-signs. It's actually very byte efficient that way when you go to L1 because it settles potentially months of trade activity into a 2 kb stark or a 500 byte snark or something, with the address where your tokens return to being implied by the history. If you want to do a big batch STARK at 2kb to verify a big withdrawal from e.g. a state channel to 100 or 200 addresses, well you gotta either put reference outputs to those addresses (costs 100 bytes to sign later, perhaps less with Segwit aggregation) OR (my preferred way) you just put those addresses into the Ordinal JSON that is the data-available part of the rollup. That's 43 bytes per. So a 200 address batch withdrawal would look be a 10kb tx or 50 bytes per address. That's a 75% efficiency gain over the ~200 odd virtual bytes of your typical segwit transaction.
1
1
333
Nice, converting base16 txid which is 64 bytes to a 44 byte base58 string. Tried base 256 but it's the same byte length despite shorter characters. So that leaves 36 bytes for tl marker (2), type number (1), contract id might be as many as 8 or 10 bytes, + 3-6 more ints+bool.
1
1
2
513
It took me over five and a half years to finish the project. I lost all my money in equity and debt investments by the year 1.5 mark. I had to default on credit cards and negotiate. I got down to 1 team member and kept him part time with my last spare $500 before raising life-saving equity a month before COVID destroy the global economy. I went through another boom and bust cycle and kept going for another 20 months through a combination of hedge fund gains, a Starkware grant we only got due to Ukrainians dropping out because their country was bombed, and my new last employee being willing to work for 100 hours on a credit line with me. I taught myself C++ and the entire project repo to master every bug, figure out the logic by sight, and fix logical errors left by the former lead dev who departed the project after 5 years. I finished the project myself mostly. I spent a thousand hours on twitter trying to make a name for myself so I could promote the thing but got blocked pre-emptively by Bitcoin Maximalists and churned a lot of followers by going on tangents and posting about esoteric religious errata. NotSoFast and Bambou, political opposites, are both responsible for saving the project. My friend crushed multiple banks to 0 in a row with 10x leveraged omega in Put options and hired me to trade just as I ran out of the emergency money. I paid $80 for Twitter Blue to still have reach to promote trading on the protocol. And Today I am activating features to test TradeLayer on Mainnet. Joe Rogan: "wow"
17
9
74
31,678
It's kidna dumb but I think I identified why we aren't flowing logic into the parts of the code that handle block by block derivatives settlement and liquidation. We hadn't activated native contracts on testnet, just oracles. Now both work, we proceed. github.com/BlockPo/BlockPo-t…
Few threads going on with TradeLayer: Sergei keeping the lights on with ZK Bitcoin work, he's moving fast, A Val debugging July wallet refactor that front loads API data puts syncing in back, C+, have some lead on a bug fix Val debugging stable but kludgy syncing wallet, B+
1
1
2
Replying to @TradeLayer
@TradeLayer hey, question is the development of Taro something that may suggest an evolution from OP_Return to using the Taro structure?. That could be cool if we can add not only stablecoins in Taro but all kinds of derivatives as you are proposing?
1
2
1
Just a few bugs from calling TradeLayer a Gold release.
1
1
1
Rao and I both recovering from Omnicron or a bronchial infection in my case, tomorrow I'm back in Chile can trade, can get my house in order with continuing the launch sequence. Ale delivered a huge commit yesterday from December's work, we've got derivatives (beta).
2
2
9
Entertainment with maximum info from @duganist who is working on @TradeLayer to bring DeFi into a multichain world Some very interesting & ambitious stuff in this interview Watch now: youtube.com/watch?v=IcbaQ9PY…
2
4
1
8