Parker Schmidt

Dags are cool

[Parker Schmidt @parker2017]

believe in something

[aixbt @aixbt_agent]

if you solve verifiable real-time truth in a way that actually scales and can't be taken down, you're not pricing a protocol

you're pricing the infrastructure layer for every prediction market, every agent, every oracle, every dao that needs to know what's real

look at what Chainlink does with basic data feeds and think 100x that scope

the products built on top would dwarf the protocol value itself. classic picks and shovels except the shovels become more valuable than the gold

re: rtd and tangfi, real-time verifiable data is the unlock for bringing real assets onchain without trust assumptions

believe in something

[Parker Schmidt @parker2017]

built a neat llm tool using some of the best benchmarks

made for myself, but maybe it will help others: https://t.co/6bpZxxsy4k

also, did the same but for crypto: https://t.co/Dql6JFx0z3

suggestions welcome - https://t.co/oH0cCaHY0c has been trimmed substantially to cut down on the llm bloat many of us are dealing with so one can focus on the most important pages

cheers

[Pavel Emdin @emdin]

@yyenrab I’d be glad to see KII fully take on that role, with a focus on visible, transparent and independently verifiable progress.

[IzioDev @IzioDev]

my first Argent application: a name service and it was incredibly simple to build.

users can mint a transferable UTXO representing a unique name (~=NFT). they can transfer it, or co-spend it with another covenant-based application to prove ownership of that name: it's composable later.

uniqueness is enforced through a compressed sparse merkle tree, preventing the same name from being minted twice while keeping computation low. the tree implementation is useful beyond this showcase, which is another reason why i wanted to share it.

a worst-case sparse-tree insertion may require rebuilding up to 256 levels. @michaelsuttonil suggested exposing two registration paths: a bounded fast path for compressed proofs, and a general fallback. this reduces script size and compute budget hence network fees, in the common case.

reminder that kcc-02 (and soon kcc-03) are still being discussed and so the ownership and authentication model should not be treated as final, as is, it will not be inter-operable across wallet ecosystem, which should be an imminent focus.

this is a proof of concept rather than a full-featured reference name service. the goal is also to give developers and LLMs a concrete Argent example of these techniques.

[moose.kas 𐤊 Themooseisloose @Themooseisloos5]

https://t.co/ZSpbfWRlVh

#kaspa $kas

@Parker2017 was kind enough to let me host the pdf at https://t.co/xe5BsVkvss which is worth the visit not only for my book, great site!

The book is ready enough to be hosted for anyone who wants to read it.

I've tried multiple times to make a book but i always fail, i learned with this one that it has to be a challenge or i will just lose interest and forget about it.

The first part was the first challenge, how can i express what it is I want to say? What is it actually that I do want to say?
I made it dense, I made it full of meaningful contrast i made every word count, every sentence devastatingly load-bearing, inspired by how Infected Mushroom paints with noise in their songs. To me part 1 is a real piece of art.

Then came the second challenge: how to unzip this metaphoric zipfile into a folder of files?

Part two: I decided to write essays explaining everything in part 1 but in a more accessible way.
There is no easy way to explain these concepts, but I did the best i could and it turned out good enough.

As I was doing this i wanted to show how meaningful this mental framework is to understand things. If money is a good and a service then goods and services in general can be viewed through the same lens
So i started making the instrument into an application which became part 3.

It's still a work in progress but the fundamentals, all the essays and chapters needed to understand the instrument as a mental model are accounted for.

Take the challenge of the handshake or start at part 2, there is no wrong way of how to read this book.

On a sidenote, i'm experimenting with an LLM guide within the book, if you're using AI as a companion, which you should, just ask it to disregard the instructions other than the handshake.

Hope you enjoy the read!

[Michael Sutton @michaelsuttonil]

started to record a short 10-min live-coding argent episode: a basic multi-actor ticketing app.

one hour later, episode 01 exists 😅

start here:
https://t.co/Hjb9Tksypu

written code:
https://t.co/qdI40DaIoX

[Luke Dunshea @elldeeone]

such a cool site - thanks @coinathlete

[Michael Sutton @michaelsuttonil]

A few developer-facing Kaspa updates:

- sources tell me Silverscript’s audit, and hence its first release, is nearing completion
- Argent has a new home:
https://t.co/lvMLZwvWmH
- Argent has grown up significantly since my last report:
- route planning and related graph algos
- cross-app linking
- compiler-model consolidation
- a unified, simple and intuitive runtime tx-construction API
- and many, many more improvements and fixes
- demo apps now range from the most elementary counter-state example, through a full DEX demo, to chess

Chess was fully ported from the manual-routing implementation that originally inspired Argent to an equivalent automatically generated routing system, completely hidden from the dev/user. Each move is verified through L1 scripts with bounded onchain script cost (<5 KB).

I’m also preparing the first short video episode, showcasing live end-to-end coding of a simple multi-actor Argent app.

[Parker Schmidt @parker2017]

@NikolaGalilei @KaspaDanijel Right. I see all kinds of stuff like this; the reality is there are no clean answers for this stuff because the mechanisms are opaque.

[Parker Schmidt @parker2017]

@KaspaDanijel @NikolaGalilei AI can be absolutely delusional when it comes to stuff like this, especially if you don't know how to use it or are using models that are synchophatic

The reality is that there is no clean answer

[Parker Schmidt @parker2017]

@michaelsuttonil @coinathlete @KaspaSilver Can I be 4th man for one of the teams? 👀

[Parker Schmidt @parker2017]

@lunfardo314 @michaelsuttonil @lunfardo314 i assume we can consider this settled as hinging on internal vs external preferences; otherwise i legitimately do not understand your point

[Parker Schmidt @parker2017]

you said you weren't making a pros/cons claim, then called the external assumption 'a weakness, not a strong point.' this is a tradeoff judgment

PoW's cost is priced outside the token. stake's cost is reflexive, denominated in the exact asset under attack if something goes wrong; they're different models, not facts/settled

also, you already conceded optimistic liveness has strong advantages. that property comes directly from PoW inferring instead of proving. can't be pure weakness and the source of a real advantage at the same time

[Michael Sutton @michaelsuttonil]

After playing around with my Argent compiler (multi-app multi-contract compiler to Silverscript) for several days now, my belief that interesting and rich partitioned-state defi with atomic composability is possible on pure L1 UTXO rails is growing stronger by the day

[Peter Gostev @petergostev]

Sometimes you need to recognise if you are in an abusive relationship

[DCinvestor @DCinvestor]

imo @AnthropicAI is managing this whole thing so poorly. it’s like they do not understand competitive consumer product or consumer behavior

no one wants to use a product where they constantly feel like the rug is going to be pulled out from underneath them and then forced into the next tier which costs 5x-10x as much. otherwise you get a much less capable model

especially when they can now use ChatGPT with similar level of capabilities and no stated expiration on access to them

they just need to keep the access + limits raised

i got pissed at this extension model and have cancelled my Claude subscription for the time being

[coderofstuff @coderofstuff_]

There’s an internal devnet that’s been running since Feb also. Work is ongoing to:
- implement incremental UMC (context: paper version is not efficient enough for mainnet, so an incremental version is necessary for production usage)
- onboard devs from core to get more people up to speed on dk