saefstroem

🚨 New Episode w @emdin & @argonmining from @Igra_Labs "Right NOW Kaspa NEEDS IgraLabs!" In this episode, Ankit sits down with @emdin and @argonmining to dive deep into Igra mainnet and role of Igra with the $KAS Ecosystem. One year after their first conversation on @xximpod, @Igra_Labs has gone from an unknown project to a live Layer 2 on #Kaspa and the conversation is as exciting as ever. The episode covers what's been built and what's coming: 🔷 Mainnet is live 🔷 Attesters & Node Economics 🔷 Ultra Light Nodes 🔷 Ecosystem Deep Dive 🔷 The ZAP Token Auction 🔷 Exchange Listings 🔷 Igra's Role in the Kaspa Ecosystem CC - Projects we discussed @ZealousSwap @AppKaskad @KaspaCom @KaspaFinance @KastleWallet @AporiaExchange @Kaspa_KAT @VivoorKAS @overpassfi @asaefstroem #KASWARE Did we miss anyone @argonmining ? Please if you could tag below :) ------------------------ DISCLAIMER This video is for educational and informational purposes only and is NOT financial or investment advice. We do not recommend you to buy or sell any assets. Opinions of guests are their own and do not constitute endorsements. Cryptocurrency and blockchain investments are highly risky and can result in total loss of capital. Do your own research and consult licensed professionals. The channel and its hosts are not liable for any investment decisions or losses.

@DankoWeb3 @PolymarketTrade @Polymarket Fair enough

@asaefstroem @PolymarketTrade @Polymarket But… u made $$$ Money is money But I completely agree with you bro it's impossible to scale this up - I use this strategy to earn $200-300 per month

A 40 year old Nobel Prize formula vs Polymarket degens pricing by vibes 99% of traders don't know that stock price markets on PM are literally binary options and Wall Street has been pricing these with Black-Scholes since 1973 I found a 7% edge Full breakdown inside🔽

@DankoWeb3 @PolymarketTrade @Polymarket I literally did this by hand a few weeks ago. Wrote black scholes merson to check the IV on polymarket vs. the one I have. In most cases its already priced in well. I made a few 100 usd, but its not scalable.

That's why you won't be able to make millions from this That's why it's not a money button When people write AI slop, it's bad When people write about something interesting, it's bad Although I specifically wrote about these problems on my article It works - rarely, but it works And you can keep crying that it's crap

Mostly disagree with this video. 1. You need harder problems. 2. Who will you hold accountable when the AI slop fails? 3. Vibe coded apps that are known to be vibe coded will not be taken by institutional funding. 4. AI accelerates our job as senior devs by reducing repetitive work, the easy button is tempting, but my clients recurrent job rate is more.

I was a 10x engineer. Now I'm useless.

@Privacygateway_ Really interested in this! Would appreciate an invite code!

This is how your prepaid card will appear in PrivacyGateway. Simple. Private. Ready to use.

@NguyenDat_TSVN There are basically a group of people that are taking over the development of the project.

@asaefstroem I thought that the decentralized project could not have investors or there was any problem here that I did not understand. Can you explain better?

Stroem.finance, the $KAS - $ETH atomic swap protocol is being acquired by a private investor and will be rebranding to Hashlock Finance. Everything I’ve proven so far, the P2P infrastructure, sub-3-minute settlement, the CCR mechanism continues under this new brand. If anything, it accelerates things due to the larger resource availability.

Any further information can be inquired directly from now on at: @hashlockfinance Thanks 🙏

I’ll be stepping back from day-to-day operations to focus on zero-knowledge research and contributing to core parts of $KAS. There’s a lot of work to be done at the protocol level and that’s where I want/have to put my energy. Stroemnet is in good hands now.

At last. $KAS

@Max143672 Nice one Max!

DONE. Just completed an initial working implementation of a based zk covenant/rollup with KAS canonical bridging (over TN12 capabilities). This work is part of the covenants++ hardfork milestone roadmap(gist.github.com/michaelsutton/…) The work is scoped as PoC however all significant challenges related to canonical bridging have been thoroughly addressed and the implementation is already mature. The vm itself is a simplified account model supporting only 3 actions: entry/transfer/exit. Notable changes and improvements over the described research spec: - Uses the new covenant ids scheme for unforgeability - Uses an additional covenant script for succinct claim-based outbox/exit ops - Implements a clever shortcut between entry and exit ops without going through the state transition singleton UTXO for streamlined UTXO management Branch: github.com/biryukovmaxim/… Demo: github.com/biryukovmaxim/… Book: biryukovmaxim.github.io/rusty-kaspa/ch…

@hashdag @maxibitcat @michaelsuttonil Yeah, agreed. imo if PoW is used then I think voting against majority should impact your chances of becoming blue, or something similar so that we incentivise honest voting mechanism.

@asaefstroem @maxibitcat @michaelsuttonil could be, not ruling that out, but an argument needs to be spelled out, what type of security this adds over honest majority (which anyways needs to enforce the slashing)

$kas What exactly is stopping us from building a prediction market in silverscript, using a bunch of community members in a multisig as an oracle? Can't be worse than freaking Polygon

@hashdag @maxibitcat @michaelsuttonil In order to support this there needs to be a penalising mechanism for producing a vote that is not in line with the majority. Simply placing it in coinbase tx payload, would not be enough.

@maxibitcat My intention was to use the payload of the coinbase txn, so no new opcode needed (plus the new sequencing commitment that @michaelsuttonil kipped makes it easier to reference these txns in separate)

@NEEDcreations So you gave up?

I resigned from Bitcoin Core on Monday. Here is the letter I sent to the mailing list: Dear Bitcoin Core Development Team, I am writing to formally tender my resignation from my position as a contributor to the Bitcoin Core project, effective two weeks from the date of this letter. Over the course of my involvement, I have dedicated significant time and effort to advancing the protocol in ways that align with Bitcoin's foundational principles as outlined in Satoshi Nakamoto's whitepaper. However, recent developments and ongoing discussions within the team have led me to conclude that my continued participation is no longer tenable. This decision has not been made lightly, but after careful reflection on the direction of the project and its adherence to Bitcoin's core ethos. The primary reason for my departure stems from a profound disagreement with the prevailing mindset among many developers, who appear to have lost sight of Bitcoin's fundamental identity as sound money. Bitcoin was conceived as a peer-to-peer electronic cash system, designed to empower individuals with financial sovereignty free from centralized control. Yet, the focus has increasingly shifted toward technical complexities and features that dilute this vision, treating Bitcoin more as a speculative asset or a settlement layer for spam rather than a medium of exchange. This misalignment undermines the very purpose of Bitcoin, and I cannot in good conscience support initiatives that prioritize scalability gimmicks or layer-two solutions over preserving its role as money for the world. Furthermore, I have growing concerns that the development process has been compromised by external influences, whether through funding sources, institutional pressures, or ideological biases that favor control over decentralization. These compromises threaten the integrity of the protocol and erode the trust that the community places in Bitcoin Core. It is with regret that I step away, but I believe this action is necessary to maintain my personal commitment to Bitcoin's original ideals. I wish the team success in future endeavors and hope that a course correction can restore the project's focus on true monetary innovation. I am available to assist with any transition matters during my notice period. Signed, NEEDcreations

We're running adversarial testing before testnet/mainnet. If you know any #Solidity $ETH security researchers who like breaking things, send them our way 👇

1. Your name is ”KaspaTeacher” implying that your account is dedicated to education of Kaspa. 2. From time to time you post news as if you are a news outlet. 3. You have significant amount of followers. Do you think it shows a good image of $KAS as an ecosystem when you say such things? You should realize this post damages the credibility of the Kaspa ecosystem as a whole. There many wrong things that Shai has done, but that does not justify attacking him on a personal level.

@KaspaTeacher It is disgraceful of you to post this from an account dedicated to $KAS education. Completely unprofessional and reckless regardless what Shai has done and what his opinions are.

@michaelsuttonil @CryptoAspect The fact that it accesses the DAA score at which it was accepted is fine, this is understood. @CryptoAspect highlighted the importance of taking into account potential future bps upgrades when utilising the opcode.

There’s a confusion here. The proposed OpInputDaaScore opcode does not access the current DAA score but rather the DAA score at the time the input UTXO was accepted (which can be years ago). This is available only bcs the UTXO entry holds this information. So median time is not something you can obtain for an old UTXO. The median time discussion is only relevant if we introduce opcodes for accessing *current* DAA score. As a matter of fact, both current DAA score and current timestamp will be available via the sequencing commitment, so they will be available to zk guest programs via witnesses, but making them accessible directly in the script engine for inline execution would be another feature

Another day, another opcode. OpTxInputBlockDaaScore, now renamed to OpTxInputDaaScore is something that I am trying to enable on #Kaspa. This particular opcode is interesting because it introduces a completely new dimension in $KAS transactions. Namely, the temporal dimension. 🧵

@michaelsuttonil @CryptoAspect I see so that wouldn’t even be an alternative, then it’s settled. Thanks for your clarification.