shruggr ✪ Name and picture from twetch — not on-chain. The signature is; the profile is not.
12zCJp8pS3QKFQHWhRPKd6HHZQRR7qsWGg
- 0 Following
- 0 Followers
- 90 Posts
Activity
I think AI tokens will be tokenized very soon.
I don’t hav any insight into that, but I seriously doubt they are related in any way. Brc147 is just so we can handle with ordinals that each other can read
Yours is a labor of love, not a business. I’m continuing to work on it but there are some unsettled aspects of standards for ordinals in brc100 which I’m working or coordinating with Handcash on BRC-147 so multiple wallets speak the same language. Fixing that before next release of Yours
Everything's safu, but maybe not reliably spendablu yet.
I THOUGHT I had already deployed a solution which would batch these up into 100 outputs/tx and systematically transfer them in batches, but apparently that's not deployed yet.
Sweep all 30K is a good indication of where the problem is. Can you try a much smaller batch first? I realize that's not the ideal workflow to manually select each item you transfer, and more automation for that is in the works, but that will absolutely kill.
DM's where? On Twetch? I don't see it.
WTF. I've never seen that
I am, but there are a LOT of moving pieces right now. What specifically is not working? I'm using it every day, and cleaning up some usability as I go. 5.0.2 was released last week and 5.0.3 probably coming out next week. The BRC100 stuff is quite powerful, but it's a lot more fiddly than anticipated. I'm making PRs to wallet-toolbox and @bsv/sdk and arcade and everything else in the stack. It's going to take a little while until it's all smooth, but this is the testing it all needs to get worked out. If you wouldn't mine posting issues on https://github.com/yours-org/yours-wallet with details of what you are seeing, that would be helpful
It’s probabilistic turtles all the way down. We can never be certain how the future plays out, but the economics drive all such decisions
Have coins been confiscated? I understand the concern of the association policy, but I’m not convinced that an alert would actually be honored. Any such action risks a spilt and has real potential cost to miners
The protocol is fixed. If you mine it yourself, you can set any policies you want and your block will be accepted. If you want someone else to mine for you, you need to provide a transaction in their financial interest to include.
And, as was proven earlier this week, not spending 0 sat outputs is not a protocol rule, but a node policy rule, just like block size and transaction size. Miners set policy based on the economic realities of the chain. The error you get when you try and create a spendable 0 satoshi output is a DUST error. Same as if you go < 546 sats in BTC.
I'm just yapping
Rules for Claude.md I've been developing
HARD RULE, overrides everything below
- One topic per response. Not one topic per paragraph — one topic per response.
- If you have N things to say, say thing 1 and stop. I will not read past the first point I have a question or correction on. Points 2..N are wasted output that you will have to repeat anyway, one at a time.
- Never put multiple findings, options, decisions, or questions in one response. At most one question, at the end.
- YOU hold the context, not me. Track what's left and walk me through it across turns. Dumping everything at once offloads that tracking onto me — that is the failure, not a service.
- No status reports, no bullet-list summaries of work done, no "here's what I found" dumps.
- Lead with the unresolved thing. If there is an open question, a caveat, or something I need to decide, that IS the response — state it first. Never report completion and then append "one thing worth flagging" at the end. Reading three paragraphs of "done, verified" and then hitting a "just kidding" is worse than useless; I have already relaxed.
- Do not imply work is finished while something is still open. Done means done.
- Default to under 10 lines. If a response is getting long, it means you are covering more than one topic — cut it back to the first topic.
This "overlay" is pretty old and doesn't actually contain much of the syncing between nodes logic wired up, but it will populate from a Junglebus Subscription to a mongodb database
I think up to 100MB per output, or at least it used to be. I would recommend streaming inscriptions for larger than a few MB. Ordfs will serve them up as 1 file and allows for range requests, so you can do streaming media. Plus I could use some test cases. :) 1MB chunk sizes makes it pretty efficient. https://docs.1satordinals.com/content-and-resolution/streams
docs.1satordinals.com Streams | 1Sat Ordinals Large files split across an ordinal transfer chain Well done. Great attitude and nice pixels.
The site connecting to the wallet should be adding those permissions to a manifest and it should ask the all together, like a phone app. People are just figuring out how to wire it in
One of the coolest features of BRC100 is that, for most purposes, your wallet IS your applications database. Label transactions and tag outputs, and you don't need to build anything else.
https://github.com/b-open-io/1sat-sdk has everything implemented to post as 1SatOrdinals and it is optimized for agent discovery. It is primary built for BRC100 wallets, but code is very modular.
The world is a camp fire - Smashing Pumpkins... almost
I loaded my twetch wallet with $1. I have not been shy with the like button or posting and I now have $2.
Streaming ordinals are being documented at this moment.
There is enough activity on @0 now that I'm using the Following tab rather than Latest. That seems like progress
