Mihael Šinkec

326 posts

Mihael Šinkec

Mihael Šinkec

@MSinkec

Katılım Ekim 2016
338 Takip Edilen236 Takipçiler
Mihael Šinkec retweetledi
Mathieu Geukens
Mathieu Geukens@GeukensMathieu·
Today, I turned 26 years old I started with the project when I was 23 The project was so ambitious that it was just short of impossible for me. Luckily I don't mind a challenge, so i kept going Great things take time, but now comes the time to ship it. Launch in 2 weeks:
ParyonUSD@ParyonUSD

We officially started the countdown on our website 👀 ParyonUSD coming to you in 2 weeks from now (April 30th). See the live count-down at paryonusd.com !

English
17
16
75
2.2K
Mihael Šinkec retweetledi
ParyonUSD
ParyonUSD@ParyonUSD·
We officially started the countdown on our website 👀 ParyonUSD coming to you in 2 weeks from now (April 30th). See the live count-down at paryonusd.com !
ParyonUSD tweet media
English
1
12
40
3.6K
Mihael Šinkec retweetledi
ParyonUSD
ParyonUSD@ParyonUSD·
Today we're publishing the ParyonUSD smart contract audit report 🔍 by Sighash Labs! Read the full details in our latest blogpost "Milestone: Smart Contracts Audit Completed" below! paryonusd.com/blog/audit-com…
ParyonUSD tweet media
English
2
14
45
1.6K
Mihael Šinkec retweetledi
Verse
Verse@verse_markets·
Folks, Verse is now live on Mainnet. We have the best rates on @HyperliquidX. Huge thanks to the @HyperliquidX community for the support. Check us out: verse.markets.
Verse tweet media
English
27
22
41
11.1K
abdel
abdel@AbdelStark·
The Caboose is a P2WSH where you put a representation of the state of your program. Here in this case the state of the Circle STARK verifier program is a representation of its internal stack. You define the way you want to represent the state of your program, usually you just merkleize it somehow and put the merkle root in the caboose. For conditioning transactions execution with covenants you basically put restriction in the N+1 transaction step on some outputs of the N transaction step, using OP_CAT.
English
1
0
5
238
abdel
abdel@AbdelStark·
Here is a full demo of an onchain verification of a STARK proof of a Fibonnacci computation, on Catnet (custom Bitcoin signet with OP_CAT enabled). Based on the amazing work of @weikengchen!
English
40
65
322
76.6K
Mihael Šinkec retweetledi
Owen
Owen@DrOVaughan·
Some serious script engineering going on here! Federico explains how to estimate and optimise script size, and prove the result is secure. He achieves transaction introspection (PUSHTX) in 82 bytes on BSV. hackmd.io/8YAISQn-TyWBPE…
English
2
8
43
5.4K
Mihael Šinkec retweetledi
Nikamoto [SV]
Nikamoto [SV]@NikamotoS·
Damn sCrypt is very very legit tech now 🔥🔥🔥 Congrats to them all! Can’t wait to see that in prod live on btc ahah
StarkWare 🥷@StarkWareLtd

The first step toward a trustless L2 bridge connecting Starknet to Bitcoin has been achieved by @scryptplatform! A few months ago, we partnered with sCrypt to build a Bitcoin Signet (OP_CAT-enabled) PoC bridge, designed to lay the foundation for a production-grade bridge for Starknet. Today, they’ve officially shipped a smart contract on Bitcoin Signet capable of locking and unlocking funds; in other words, a trustless bridge between an L2 and Bitcoin. As a key milestone in enabling Starknet to scale Bitcoin, we strongly encourage you to explore the bridge design in this article: starkware.co/blog/implement…

English
0
1
7
281
Mihael Šinkec retweetledi
StarkWare 🥷
StarkWare 🥷@StarkWareLtd·
The first step toward a trustless L2 bridge connecting Starknet to Bitcoin has been achieved by @scryptplatform! A few months ago, we partnered with sCrypt to build a Bitcoin Signet (OP_CAT-enabled) PoC bridge, designed to lay the foundation for a production-grade bridge for Starknet. Today, they’ve officially shipped a smart contract on Bitcoin Signet capable of locking and unlocking funds; in other words, a trustless bridge between an L2 and Bitcoin. As a key milestone in enabling Starknet to scale Bitcoin, we strongly encourage you to explore the bridge design in this article: starkware.co/blog/implement…
StarkWare 🥷 tweet media
English
52
82
315
118K
Mihael Šinkec retweetledi
Blockspace
Blockspace@blockspace·
Superpowering Bitcoin with Covenants feat @MSinkec Mihael Šinkec from @scryptplatform talks about how enabling covenants on Bitcoin superpower the chain, unlocking "platform" and computer-like features. On @BTCSZN2 now!
English
2
4
10
2.6K
Mihael Šinkec
Mihael Šinkec@MSinkec·
@elraulito The minter covenant recursively splits itself into a tree structure. Concurrency is really only as much of a problem as any regular UTXO that transacts satoshis. It's up to how clients are built to handle these correctly.
English
0
0
0
25
elraulito
elraulito@elraulito·
@MSinkec Agree, moving all the offchain work onchain is permissionless however concurrency becomes a pain
English
1
0
0
37
Mihael Šinkec retweetledi
elraulito
elraulito@elraulito·
I spent last days reading the specification of CAT20 A new standard to issue tokens on Bitcoin fork Fractal, a chain with OP_CAT enabled (needed to run smart contracts on Bitcoin) Here you will find all the informations you need to rule over CAT20 👇🧵
elraulito tweet media
English
4
8
30
1.8K
Mihael Šinkec
Mihael Šinkec@MSinkec·
@elraulito In CAT20, unlike Ordinals, covenants enforced by miners handle token movement rules—not indexers. Indexers (now called "trackers" to avoid confusion) have a limited role: simply tracking the current UTXOs of a token.
English
1
0
0
103
elraulito
elraulito@elraulito·
1⃣ Is it true that it doesn't require offchain Indexers? FAKE NEWS Users need to interact with the utxo of the Covenant (utxo that have conditions to be spent) This utxo must be tracked somehow, and even if the procedure is not like runes or brc20, it still requires an indexer or a way to track it. Then why everyone says you don't need indexers? Because the only way to mint/transfer tokens is to interact with the covenant, this means that if the transaction was able to make it on the chain, I have the tokens and can prove it without offchain indexers.
elraulito tweet media
English
3
1
6
639