Nikamoto [SV]

I wrote a Lisp->Script compiler for #bsv Thanks to feedbacks from early testers it should be ok to use. So here is the documentation: replit-docs.frenchfrog42.repl.co It has a link to a "repl" where you can use the compiler (no download required) If you have any feedbacks, let me know

Damn sCrypt is very very legit tech now 🔥🔥🔥 Congrats to them all! Can’t wait to see that in prod live on btc ahah

Damn 👀👀👀👀

@scryptplatform What's something cool to build? Has someone already built an AMM like uniswap for ordinals on bsv? (I believe no) Would that be relevant?

AMA on the ongoing hackathon scrypt.devfolio.co

@sinoTrinity We have OP_LEFT OP_RIGHT OP_SUBSTR on bsv? There are not on the wiki 👀

It works partially on BTC and fully on BSV, since the former disabled many opcodes, which have all be reinstalled in the latter

@MSinkec It works on btc too? Or just bsv? Nice nice

@NikamotoS docs.1satordinals.com/ordinal-lock

Ok too much hype on the brc20/ordinal thing Is there something interesting to build there with SCRIPT? Would be very nice if I can leverage my knowledge of script to build something

@Kltzoh @RadiantLayerOne @NovoBitcoin Radiant finally have a l1 token? With a wallet?

@NikamotoS @RadiantLayerOne @NovoBitcoin Well this aged well

Which one will have first an L1 token between @RadiantLayerOne and @NovoBitcoin?

@mattrickard The fuzzing idea is interesting. Do you have any intuition on how it would look like? Any project trying to build that right now?

Copilot is the tip of the iceberg when it comes to LLMs on code. How we might accelerate the developer workflow through language models... • Merge conflict resolution. Most merges go smoothly – changes can be cleanly rebased on top of the main branch. But other times, two developers have made irreconcilable changes to the same file. It's difficult to automatically resolve changes like two developers updating packages or even renaming a file. Some of these changes are context specific (where the context isn't recorded in version control), while others require knowledge of languages, frameworks, or some higher level concept (e.g., a package file format). ML models might plausibly learn these patterns and perform higher-order semantic merges. • Automatic linting and style checking – Developers often keep their code consistent with chosen linting rules – tabs instead of spaces, no unused variables, or other best practices that aren't enforced by the language itself. In addition to linting, there are stylistic suggestions that are often caught at code review time – how logic is split, documented, or called. Could we automatically encode some of the style of a particular project or company to reusable rules? • Placeholder documentation – Documentation is often an after thought on tight deadlines and understaffed teams. Some engineering cultures mistakenly value shipping code much higher than lowering the cost of maintenance. LLMs can stub documentation for functions that's understandable and mostly correct. While it will likely never reach the quality of hand-written documentation, it could serve as a placeholder for documentation that can greatly speed up the time-to-document code. • Project scaffolding – Starting a new project requires boilerplate folder and file creation. Even if you use a template (like create-react-app), there's a lot of customization you might need. Could LLMs provide suggestions on folder and file structure as well? Perhaps understanding import cycles and suggesting package boundaries or file boundaries? This is a task that is difficult for even the best developers – applications are constantly changing and shifting their scope of responsibility and thus where the logical boundary should be. • Test suites and fuzzing – Copilot can already generate test cases, but what would a LLM-first fuzzing library look like? • Infrastructure as code – Copilot already does this to some degree, code is code. But maybe there's a chance to automatically infer this from the project code. "Self-provisioning" infrastructure. This has been attempted many times before and always failed – usually at the language level.

6/ the validators need to go off chain to begin discussing what to do! Where do they go? Discord! 👀 They then need 66% of validators I believe to agree on a solution to get back up But what if many aren’t available? Maybe sleeping or just unavailable? 🤔

@nicoolas @CryptoMafiaFR Ces entreprises peuvent décider d'arrêter de racheter leur propre action et/ou décider d'en émettre pour en revendre. Si le prix de l'action fait x100 c'est ce qu'ils vont faire (et ont fait pour AMC/GME/... je crois) Mais la l'émission des cryptos change jamais en théorie

@CryptoMafiaFR Il y’a bcp mieux avec un tas d’actions qui non seulement te verse un revenu mais dont le dénominateur baisse dans le temps. La comparaison avec les Fiat n’a aucun sens

Mathématiques de base : Votre argent $ USD = —————— ♾ Votre argent #BTC = —————— 21,000,000

@sam_holmes @sinoTrinity @Dr_CSWright Why would there be a diff between an opcodes and a pseudo opcodes? The latter is just multiple opcodes so shouldn't be really different, no? Or maybe because push_tx uses the way the preimage is computed, whereas an opcodes wouldn't?

@sinoTrinity @Dr_CSWright OP_PUSH_TX isn’t really an op code; it’s a pseudo-opcode. So, one could argue Bitcoin Script, and therefore Bitcoin, isn’t TC. But what I say is, who cares. It can do what a TC can do, and it’s empirical.

Another independent paper proves Bitcoin is Turing Complete by simulating any counter machine: Computationally sound Bitcoin tokens ieeexplore.ieee.org/document/95052…. It requires changing Bitcoin script to include covenants, which is actually not needed because of OP_PUSH_TX. @Dr_CSWright

@Rob_GCC Congrats 🥳

@ilythos @delocaliz Merci! C'est clairement loin du centre de leur ville mais ça a l'air sympa en effet

@NikamotoS @delocaliz propertyguru.com.my/property-listi…

@delocaliz T'as pas t'es dm d'ouvert?

@NikamotoS Dm moi 🙂

@AgoLajko Like what? Healthcare? I'm open to change my mind, but it feels like that Europe could compete (not in a fair way for sure) with US based startups, so these startups just sell at lower price in Europe to avoid the competition Sorry if you're talking about smth else ahah

I don't like subsides, and hate how historically the US has subsidised everything for us in europe

"Track unique number" -> may be a solution to b2g Anon please try :))

@sam_holmes @Bitcrash4 It was 32mb For opcodes, I think the shifts are different Also the preimage is different I believe And that's it I think

@Bitcrash4 Didn’t the original Bitcoin have a block size limit? Or was that added later?

I think there is a major problem here. BTC makes Bitcoin look bad. For anyone who doesn't know. BSV is the original Bitcoin. BTC is not Bitcoin.

@ProjectBabbage After you clicked "ive saved it" some wallet ask you 3 random words from the 12/24, and you have a *go back* button to go back to the screen with the words

Any thoughts on how to convince MetaNet users that they should definitely, totally, 100% save their recovery keys, and like, not click past this until they do?

@rodarmor Btw when a smarter algo to construct these blocks? 👀👀👀 I think the current algo is the naive greedy of backpacking, picking the best fee/size first, but with ordinals you'll miss some interesting blocks with it

gobsmacked