Ted Ian Osias

TVL is growing @RolluxL2

2 days ago @syscoin had this event happen to its network. @binance had asked and so did @HuobiGlobal in our groups if the network is fine. They depend on syscoin multi quorum chainlocks to have absolute confidence no roll backs are possible to accept deposits. There was a disruption on masternode services on @Allnodes which caused many masternodes to lose their quorum BLS shares which caused them to lose their votes to vote on the chainlocks. So yes the fact that @Allnodes runs so many Sentry nodes on syscoin is a point of centralization, but given our position in the market being sub $100m it is not a big problem but one which I think the community should work on long term. However unlike the issue that would have been caused if it were @ethereum there was no loss of funds. There was no slashing because there isn’t any weak subjectivity due to being merged mined with @Bitcoin we use PoW consensus for block validity and only use chainlocking for finality! We therefore use positive reenforcement not negative to create seniority to pay longer term Sentry nodes more rewards compared to others. It has been a resounding success even though sys price is near 52w lows still. We have been constantly and steadily growing Sentry nodes (about 35% of the supply). But why finality or chainlocking? Because we have DA and a modular design and because we are merge mined. Long standing issues around bitcoin miners willing to censor merge mined chains can be solved through finality. We still give power to Bitcoin miners to decide longest chain (aslong as it’s the first one seen as well). To try to censor would require to collude with all Sentry nodes to not chainlock + 51% attack Bitcoin mining network. We also need to prune DA blobs in PoDA to serve rollup scalability. So instead of any issues or pro activity required, the service was restored by all nodes and the network self-healed itself: Proof of disruption: { "result": { "previous_chainlock":{ "height": 1765120 }, "recent_chainlock":{ "height": 1765400, "known_block": true }, "active_chainlock":{ "height": 1765125, "signers": "07", …… You can see the locks stopped for a few hundred blocks, the network fell back to standard nakamoto consensus (longest chain rule). It was at worse the same as Bitcoin using Bitcoin hash rate to secure the longest chain. Exchanges were informed to continue business as usual, just extend confirmation required to 10-12 instead of depending on the chainlock. Now network healed by itself and they can depend on chainlocks again. The takeaway is: 1) finality is great and required for a modular network (so our DA blobs can prune after finality and so selfish mining on Bitcoin is not a problem) 2) don’t depend on finality for any new consensus that requires liveness or even security. 3) finality should be additive in security and robustness. If they exist, network works optimally, but when chainlocks not forming network should keep working (PoW style). 4) this means there is no fragility introduced when adding finality. It makes it less fragile as there isn’t any selfish mining concerns. With PoS consensus as a backbone this design isn’t possible! In fact this is THE natural evolution of extending Bitcoin through auxpow (merged mining), for modular blockchain design. We believe it is the optimal design that does not run the risk of loss of funds or using funds to secure network, you need energy to secure a permission-less organic network to solve BFT. So no loss of funds, no risk to businesses. No chainlocks no problem, we are back to optimal operation! Even with centralization, it works without risking other ecosystem participants.

@angular Didnt know there’s this feature. 😂

If you haven't had a chance to try out NgOptimizedImage, we'd love to hear why:

Requesting faucet funds into 0xa9b031f2c75d08178b7a18cecfa552bc60ee1d3f on the #Syscoin network.

Bitcoin payments accepted here in Boracay Island!

Coding by the beach.

Got some swag from @Ledger for being the developer of the month! 🔥 Thanks to @syscoin for support!

Got some swag from @Ledger for being top 1 Developer of the month last April! 🔥

Surely you jest! Nope! We've added Jest support in v16! - Jest support is one of our most commonly asked for features - Users can opt-in to run unit tests with Jest! Please keep in mind that this support is currently experimental!

Hi everyone - I am looking for a new role and would appreciate your support. Thank you in advance for any connections, advice, or opportunities you can offer. #OpenToWork lnkd.in/gYh7fS-x

@proguerra He then pulls out his QR code. 😂

Homeless person: spare some change? Me: sorry I only have crypto. 😂 😈

Had a great time today educating people about @syscoin and how we can provide economies of scale to the industry for the first time

I'm claiming testnet tokens for @zksync v2, an EVM-compatible ZK Rollup! My Address: 0x55822acc427341ecfbc740800e7428e8f8e188c0 Learn more: v2.zksync.io

@proguerra I remember our first Vibravid dinner meeting with @kilroydillon we joked around our waiter if they accepted bitcoin as payment 😂😂

The homeless are evolving. Guy comes up to my car with the cup. “Sorry bro, I don’t have any change or cash” Homeless guy: “you got cash app?” He pulled out the card so I Gave him $5 Soon they’ll be like “you got bitcoin?” 😂

This is one of the greatest videos. 😂 Happy that @syscoin is leveraging the Best through merged mining

The ending.. 😂 twitter.com/buitengebieden…

We are excited to announce that @getblockio integrated with @syscoin, the only layer-1 #Blockchain that scales with EVM functionality🙌🏼 Now #syscoin shared and dedicated #nodes are available on GetBlock👇🏼 getblock.io/nodes/sys/ getblock.io/dedicated-node… 3 words: Build on Syscoin!

@proguerra @AshleyDCan She'd be glad! 😂

@AshleyDCan 😂 @OsiasTed what if you told your wife not to code?

a short story in two parts

Having fun documenting FastSwap API used on @syscoin 's bridge in preparation our Bridge redesign. No better way to learn tech than to read code. 😂