nomadshiba⚡⚡

its me, you know

bip352 / silent payments: sp1qqf95gnrh453sncve4yal29zedxll3k48a0kcxhted66nnu5frcshwqmduw4x6a9ggvcmesah9qu32jx95ust635ng6xrd570mpu9hhmn7cpwpee5

https://npub.name

Public Key

npub1gkp4cdh5rktehjqjnqc09awey4302dpadlka6mes4fu5spes7fhqfsppqk

NIP-05 Address

me@nomadshiba.me

Profile Code

nprofile1qqsytq6uxm6pm9umeqffsv8j7hvj2ch4xs7klmwaduc2572gquc0ymspzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqgdwaehxw309ahx7uewd3hkct45dwy

Publishing to

relay.primal.net

nos.lol

nostr-01.yakihonne.com

relay.damus.io

nostr.mom

t7fu7viea27nuvo5aklpylkvv723m67znnwjxpjmcpytpcpl6nyh2gid.onion

Author Public Key

npub1gkp4cdh5rktehjqjnqc09awey4302dpadlka6mes4fu5spes7fhqfsppqk

Show more details

Last Notes

2026-07-09 08:32:01 UTC

just realized i didn't eat or drink anything for the past 2 days

2026-07-09 07:34:08 UTC

- reply

i just woke up today and thought:
maybe you can try glass shaped candy?

2026-07-07 11:25:28 UTC

- reply

i like bip110.
we should also release the cat.
we should also remove witnesses discount.
we should also lower the block size limit.
we should also have a websocket and bluetooth protocol for p2p, along side the tpc one, and support dht as well as tor and ip2 built in.
electrum endpoints should also be built-in.
pruned node options should be removed to make full node size more optimized by leveraging built-in electrum indexes.
we need a new gui as well, and built-in explorer.
plugin support also needed.

2026-07-05 12:55:05 UTC

- reply

https://bip110.org ???

2026-07-03 09:17:13 UTC

- reply

https://bip110.org/

2026-06-27 05:23:51 UTC

GM
had some good fun dream

2026-06-18 20:01:29 UTC

- reply

bip110 is bitcoin, everything else chose to split, not bip110.

2026-06-18 15:54:32 UTC

- reply

https://blossom.primal.net/691482974b5ba8ccc16ae8f0aee590936226b283fb0e5b319056f3e1fbc5e745.mp4

2026-06-09 13:20:53 UTC

- reply

did you get my reply in the dms?

2026-06-09 08:05:15 UTC

Support BIP-110 you cowards!

2026-06-09 05:22:15 UTC

- reply

hey @nprofile…s6gp throw a dm

2026-06-09 04:39:02 UTC

- reply

learn to read retard

2026-06-08 21:40:50 UTC

- reply

you didnt give any reasons, made up arguments. its ok to not know things, you dont have to try hard to appear correct.
you are constantly lying about how kaspa works and its cryptography, using meaningless jargon to appear more qualified or feel better.
read the whole thread.
if you are gonna support kaspa at least learn how it actually works.
https://blossom.primal.net/25e75bffef2b8d71f0b19f66e979d9c367eeb55482e0e4323996fd81d4e0c5b8.jpg

2026-06-08 20:28:37 UTC

- reply

Same low iq energy as:
"Oh if ethereum security is just an illusion. Go attack it. You can't"

2026-06-08 19:59:52 UTC

turns out i was right.
it really is a delusion of a solution.
#nevent1q…v24m

2026-06-08 14:46:53 UTC

- reply

you dont seem to understand my point.
you are still thinking about a decentralized network where one "bad guy" does something out of the ordinary.
thats not about that, thats about how much you can resist "official" change. the decentralization aspect.
i already mentioned your point here:
> only way you can reject it meaningfully is you are online at that time, and see the invalid (for you) tx. and out right deny the utxo set.
you make most pow the valid chain (pre-pruned), as long as miners wants a change, that change happens.
once it happens no fresh node even with an older version rejects that chain. you just ride along.
again `utxo_commitment⁠` doesnt prove the specific script was following your ruleset. it only proves utxo set was valid, and seen as valid and has been built on top of it in the past by others. not you. call it what its, which is trusting the collective, social consensus with pow.
you can accept trade offs and say, "yeah i think kaspa does enough" but you dont do that. you insist that utxo_commitment⁠ and pow means verification of past txs some how.
you even admit 51% attack could create invalid utxo for your ruleset. thats the definition of utxo_commitment⁠ cant verify tx was following your ruleset back then. it means there is consensus and work done to accept that history no matter it fits into your rules or not. that's compliance not verification.
another example if you do a temporary hard fork that get deactivated a while later, even the freshly running old version nodes follows the hard fork chain after it deactivates.
its a really simple question:
Q: Do you know every TX before you is following YOUR RULES
A: No
but you keep arguing that "no i can verify", that's just wrong, you can only trust network in large says its good.
you didnt even answered bandwidth point, even if you are are pruning you still download. and with the goal of 100bps that looks even worse. do you think someone's laptop sync with every tx ever worldwide without hogging some stuff?
you also didnt answer periodic "smooth" hardfork activations kaspa has. thats not decentralization, thats a realase schedule of dev team. everybody complies to updates. node impls auto update.
you can't know if history was valid, you just know history has big support.
when i first asked "do you run kaspa" and you said "yes", you were wrong. you dont run kaspa. you listen to the kaspa network. illusion of a node running. if you were running it you would run it from the genesis. yes you can reject blocks as long as you are live. but unlike a bitcoin node you just accept what came before you. you TRUST others before you acted the way you hopped they would act.

2026-06-08 11:03:37 UTC

- reply

proof of consensus != proof of enforcement
also maybe you cant understand it but "L1 should be slow" isn't dogma. it's the cost of letting anyone verify without permission. you can disagree with the tradeoff, but you didn't solve anything. everything works the same its 1+1=2 its the reality of the universe. you love using words like "thermodynamic" so much, its not so hard to understand. its not a bitcoin thing, its any system ever.
you started a new kaspa node fresh:
- downloads the pruning point proof (just headers, not full blocks)
- checks PoW on those headers (only for ordering/consensus, not verifying the txs inside them)
- checks ghostdag structure + blue work (only picks the heaviest proof, says nothing about tx validity)
- downloads the UTXO set from an untrusted peer (the list of who owns what, streamed to you in chunks)
- hashes that set with muhash, compares it to the `utxo_commitment` field in the header (only confirms the set matches a number a miner wrote into the header)
- validates txs in the pruning point block only (that single block, against the set it was just handed)
- everything before the pruning point: never executed (no scripts run, no signatures checked, data never even downloaded)
what verifies what:
- PoW: energy was spent on the headers
- ghostdag/blue work: this proof is heavier than competing ones
- muhash check: the set you received matches a number in the header
- nothing: that the number was produced by valid txs following the rules
the `utxo_commitment` is just a value in a header. the node confirms "the set i got matches this value." it never confirms "this value came from valid execution." consistency, not correctness.
proof of consensus, not proof of enforcement.
nodes will rejectrt `utxo_commitment` if:
- a utxo set that doesnt hash to the value in the header, meaning someone hands you a snapshot thats been tampered with after the fact. the hashes won't match. rejected
- the only thing that breaks the check is a mismatch between the bytes you received and the committed hash. basically checksum.
- only way you can reject it meaningfully is you are online at that time, and see the invalid (for you) tx. and out right deny the utxo set.
`utxo_commitment` doesnt enforce that the transactions which produced that utxo set were valid. its generated by the miner who mined that block. if devs pushes an update and miners mine based on it during a period. and days pass. you have no idea if it fits your ruleset or not. you just accept it because its the most pow.
a fresh node goes:
does my downloaded set match this hash? Yes. Accepted.
it has no way to know the set contains coins that should never have existed.
the `utxo_commitment` proves the set matches what was committed.
it does not prove what was committed was legitimate by your rules.
it catches tampering with the snapshot, not "fraud" or period of rule change baked into the history, deep enough.
its trusting the work, not verification. and assuming the bandwidth a kaspa node spends, you cant have a lot of nodes that you cant easily find one that is telling you to double check that older block. if you can find a copy of the said block of course. assuming only few big cloud runners will be running a full node soon.
source: https://github.com/kaspanet/rusty-kaspa

2026-06-07 21:53:49 UTC

- reply

"Trust the 'Science'. Even thought I don't get it fully. Because it sounds sciency~"
"Just trying to prove myself right any means necessary, mentioning things that doesn't even exist in Kaspa"
You just hear some stuff that you dont fully understand and, go "oh so thats why" *clueless*.
THE mAth doesnt "prove" what you think it proves... Or you dont know what is suppose to be proving.
you think you have some cool new solution while mentioning 40 years old papers.
kaspa literally doesn't use zero knowledge proofs.
it uses muhash commitments and sampled headers. which is a hash of a set. it commits to what the set is, not to how the set was derived.
even if it did, zk proofs require a prover. someone generates the proof.
bitcoin doesn't need a prover. i am the prover. i run the computation myself from genesis.
you invoked zk proofs to sound technical. but kaspa doesn't even have them. and even if it did, it wouldn't solve the "valid by whose rules" problem. it would just move the trust to whoever generated the proof.
you don't even know what the scripts are.... as a newcomer node.
https://medium.com/@jcroger/why-archive-nodes-are-no-longer-essential-the-kaspa-proof-f15d3b64d24a
> While you can’t prove cryptographically that pre-pruning history is valid once it’s dropped, **social consensus** ensures that if deceit happened, at least one honest node would have detected it and preserved proof. This hybrid model guarantees consistency
https://hashdag.github.io/blog/syncing
> The primary goal of consensus systems is **facilitating agreement, not enforcing consistency**. And if the economic majority happens to follow and maintain a ledger to which an invalid transaction entered at some point in history, so be it,
> Kaspa nodes prune block data by default, and new nodes by default do not request historical data, rather, they **sync in SPV mode**, i.e., by downloading and verifying only block headers.
kaspa is just the other side of the bcash coin. "fuck verifying txs, we will just have lots of txs"
honestly im tried of all "lets make L1 fast" "solutions". L1 suppose to be slow and small.
stop trying to walk around it.

2026-06-07 18:59:42 UTC

- reply

also no. you cant assume tx fits to your rules because of a "proof".
that would be the best compression ever created.
you are losing information.
its impossible.
as i said in the beginning "delusion of a solution"

2026-06-07 18:57:25 UTC

- reply

you are still thinking about someone breaking rules. not rule changes.

2026-06-07 16:58:44 UTC

- reply

there is no way you can know if someone rejected something in isolation at some point.
the commitment proves the utxo set is consistent with the history that was accepted. it doesn't prove that history was valid by your rules.
those are different things.
you still cant verify what script ran, how.
the commitment proves "this utxo set is the result of this history"
it does not prove "this history followed the rules you would have enforced"
"this utxo is valid", valid by whose rules?

2026-06-07 14:12:30 UTC

- reply

> that block would be rejected by every node online at that moment.
you are saying it yourself here "at that moment".
what rejecting a change proposed by the kaspa devs looks like? what happens if miners support the change but you don't.
also nothing blindly trusts PoW.
but with default kaspa node if software rules changed at some point for a while you would have no idea because you dont replay those txs. you just trust what the network tells you the utxo is.
if a chain has 2x of pow of your current chain in bitcoin, but has a single tx that doesn't fit into your ruleset, you wouldn't pick that chain.
but with kaspa you have no idea that happened. you either have to always online to catch it, or run and verify every tx from the genesis.
you can only prove everyone on the network agreed that valid utxo set looked like "this" at some point.
no matter how many tricks, ideas you have not to verify txs one by one for real. none is actual verification of the tx.
that's trust, not verification.
you cannot meaningfully prove anything about the past.
have fun complying to another hard-fork that activates "smoothly"

2026-06-07 11:29:19 UTC

- reply

you get the utxo from from the snapshot.
you dont verify anything to that point.
you trust pow. that's almsot exactly like spv behavior.
if a bitcoin node sees an invalid tx they blacklist that block hash because the whole block is invalid.
you can't build on invalid tx. is that so hard to understand?
you can't just download a utxo set and call it verified just because it was timestamped in the DAG/chain.
you dont even know if the chain you are on is valid.
you just pick what ever has the most pow.
because you can't verify a tx from one week ago.
you trust the utxoset your are given.
be honest with yourself.
you are claiming things that are not real. be real.

2026-06-07 10:04:54 UTC

- reply

This dude mining with 4EH/s just found 2 blocks in the last 24 hours!
#nevent1q…4jay
https://ocean.xyz/stats/bc1q3595j3lnu4ywus85p5369tq3j983fqa786p3sq

2026-06-07 07:01:58 UTC

- reply

that's exactly what i said.
i also don't like bitcoin pruned nodes but they will at a least replay everything from the genesis. kaspa will just trust the PoW as if it verifies the txs somehow. that's very similar to a bitcoin spv node.
you said it yourself, you are using PoW as a trust mechanism to pick the chain, you are not validating blocks older than utxoset snapshot. you have no idea what older txs are, you are not validating that. you have no power to go "ah this old tx makes no sense, let's blacklist this block and find another chain without it". miners and full nodes control your chain/DAG. you trust the PoW, you dont verify. that's literally a SPV node.
and starting from utxoset snapshot is not a cool feature of kaspa that's just sacrificing verification for faster IDB. why? because you produce 10blocks per seconds right now. no normal user can sync that. its terabytes of data even now.
bitcoin limits block size and time on purpose to keep the chain small. because its the global state that every bitcoin user has to verify and sync with. then we have things like lightning, ark or others that create isolated states where not everyone has to sync with. that's how scaling works in any system, not just bitcoin.
your design sacrifices sovereignty, decentralization, and verification in favor of blocks-per-second.
#naddr1qq…lzae
and i said the node you linked only connects to 9 nodes because again a normal home hardware and internet can't handle 10 blocks per second i guess. how much bandwidth does that thing spent that you/they had to lower the node count to only 9?
why not 50 nodes?
you say you are running kaspa, but all you have is a pruned SPV client with ✨DAG✨. by desig kaspa is controlled by the miners and "archival" full nodes. you dont have a power to say "no". because you trust pow, don't verify.

2026-06-06 21:28:35 UTC

- reply

every cycle its the same always, we expect it, it happens, nothing new.

2026-06-06 19:21:24 UTC

- reply

that's not running kaspa, it just a peeking node/relay.
so you're trusting a handful of full real nodes for the entire history of the chain, since your pruned node doesn't replay anything.
it just accepts a UTXO snapshot. if those archival nodes lie, you can't detect it if you weren't listening during that time.
and if the ~317 node operators wanted to change the rules, what stops them? you just had a hard fork last month that the whole community "smoothly" complied with, and the installer you linked auto-updates itself. that's not a decentralized consensus, that's a dev team with a release schedule.
also curious what the bandwidth looks like at 100 bps, since you're already throttled to 9 peers just to make 10 bps manageable on normal hardware.
it sounds like another high-throughput-first crypto project, but with the illusion of node running.

2026-06-06 17:33:30 UTC

- reply

you sound like a kaspa user, are you running the kaspa on your computer?

2026-06-06 15:08:31 UTC

if you really want yield on your bitcoin, dont play finance games.
just rent some cheap hashrate and start mining.

2026-06-06 07:22:05 UTC

- reply

are you running kaspa?

2026-06-05 10:48:23 UTC

- reply

also linux ux is more pleasant now, thanks to ostree and flatpaks

2026-06-05 10:44:25 UTC

- reply

also monero doesn't have a size limit. which i don't like as a 300kb blocks supporter.

2026-06-05 10:33:20 UTC

ok work coding stuff is almost over.
100% done tonight.
then i continue making the atlas!!!

2026-06-05 07:36:28 UTC

people play with all kinds of bitcoin, crypto, and fiat games, but can't just buy bitcoin.
then they complain about the state they are in.

2026-06-05 07:00:26 UTC

Fountain is cool.
but wish it was nostr native.

2026-06-04 18:16:04 UTC

- reply

@nprofile…2jpv didn't look at it myself yet, but you asked something like this i right?

2026-06-04 16:27:15 UTC

follow your solar weather

2026-06-04 15:55:06 UTC

BTW I made this few months ago. Some sites dont support Nostr Remote Signers like Amber, only support browser extensions.
This extension acts as a Browser Nostr Signer but bridges the connection and let's you actually login with your Remote Signer instead.
https://chromewebstore.google.com/detail/remote-nip-07/dkeaighngpmilhnepghmdfjlmlgaomcl

2026-06-04 12:12:22 UTC

- reply

as always take the ideas, dont make heros.

2026-06-04 12:06:08 UTC

- reply

it changes based on the scale, the project, and the architectural complexity.
i cant think about "vibe coding" my personal projects, for example.
i also get my hands dirty at work once in a while. even when im not manually typing, i still have to verify the architecture the LLM created, explain the design in my head, how the code should work, etc. i cant imagine someone less experienced doing that well.
there are also things that require "inventing" like innovative game development, where you have to come up with new tricks, reduce allocations, make things faster, find new solutions. where LLM biased towards applying known solutions instead of creating domain specific solutions. they dont come up with an idea while in the toilet.

2026-06-04 11:50:45 UTC

- reply

im rarely motivated about the work code, so i kinda like it.
leaves me more time for my own projects.

2026-06-04 11:49:06 UTC

- reply

OMG LOOK AT ALL THESE PROFITABLE HASHRATE UNDER THE HASH VALUE, GO RENT IT.
https://blossom.primal.net/c42a579b2e8b3b775c05cec86f63e94372e101d032de4ad2d2a802853cc9ec1e.mp4
#naddr1qv…7rzv
#naddr1qv…89ss

2026-06-04 11:43:54 UTC

- reply

gonna make my own DE somewhere next year. fuck this shit.

2026-06-04 11:42:32 UTC

- reply

some dumb thing, hard-drive manufacturers started doing first years ago.
then apple started using it, and now some Linux DE(s) are started to use it...
it was fine when it was just Apple, but wtf Linux...
so annoying.
NO BODY USES 1000s it makes no sense. its a lie.

2026-06-04 11:31:56 UTC

you guys code to get employed?
i have nothing against people but.
people "learning to code" to get employed somewhere tires me so much.
when we used to talk about programming it was about building things, optimizing things, ideas, discovering new ways etc.
now if you mention programming people are like of yeah the job title: programmer. i mean i work but that came later. i work because i know it, and i need money. i dont code because i need money. i code because i gotta build.
if i had a lot of money, i would be coding more.

2026-06-04 11:14:58 UTC

clients should warn people about non-blossom uploads.
they can be tampered with, cant be verified. (unless they have the file hash in the event itself as well, i dont remember the nip)
i know many people use non-blossom cdns, but thats the points. the warning should scream to their face.

2026-06-04 11:06:52 UTC

- reply

yup thats the issue, you are using a blossom server, but its not in your blossom server list.
so probably clients are treating it as just another cdn. doesnt verify it.
this also means when you upload it, you dont have mirrors of it on other blossom servers.
https://blossom.primal.net/2843c145008363f280d68eb16c80a9352d704a100908b68ef98768b1ee47909b.png

2026-06-04 10:57:02 UTC

- reply

blossom should verify the hash. then should look at other blossom servers.
this is kinda weird the client is even letting us see the image while the hash doesnt match.
maybe its not a blossom? just cdn?

2026-06-04 08:28:28 UTC

- reply

Don't sacrifice decentralization while its the goal. #naddr1qv…zgf8

2026-06-04 06:39:13 UTC

I finally understand Kaspa.
It's a delusion of a solution

2026-06-04 06:33:04 UTC

i have the fact that MiB, GiB etc exists...
when you say 1MB nobody knows if you are talking about 1000KB or 1024KB...
storage people can do mess it up.
we should have just kept using 1024 without "i" in the middle.
instead of complying.
so keep calling 1MB a 1024KB.

2026-06-03 16:49:58 UTC

- reply

i think they did on purpose, it literally activates right after diff adjustment. the next block.
probably not to produce too many blocks without proper hashrate.

2026-06-03 16:31:49 UTC

- reply

i believe 110 activates after diff adjustment.
so diff won't go down if it can't produce enough blocks to the next diff adjustment. which is kinda hard.
unless it has some good hashrate.

2026-06-02 10:46:04 UTC

"people pick heros, not ideas. thats the issue" - me

2026-06-02 06:21:11 UTC

GM
are you nostr only, mainly?

2026-05-31 11:46:15 UTC

i have been moving my braiins hashpower bid order 10 times a day, so i can maximize my efficiency

2026-05-31 09:11:00 UTC

GM
https://blossom.primal.net/9d7f2719ef15bc417448a2bcc4682e6cdd85eab38ea5825e30a0c99808f4555d.mp4

2026-05-29 06:13:28 UTC

- reply

@npub12rv…85vg cant even understand bip110.
it activates after the diff adjustment.
it wont fork off.

2026-05-29 05:58:35 UTC

https://youtube.com/watch?v=MN2IyhyMZBU

2026-05-28 09:14:54 UTC

- reply

3,004,486 sats spent so far.
2,992,865 sats lifetime earnings.
-2,069 sats pre-braiins earnings with bitaxe only.
108,177 sats estimate rewards in the current window
= ~3,098,973 sats total earnings
so +3.14% in profit

2026-05-28 07:43:33 UTC

- reply

yes.
nobody "ask" for that much its all at 40k sats range. all you have to do is place it somewhere in the green, preferably lower than the hash value or as close to it as possible. they are just overpaying for nothing.
i think the ui confuses the people.
or they dont understand how it works.

2026-05-28 07:35:54 UTC

I HAVE A QUESTION
who tf is paying this much for the hashrate
https://blossom.primal.net/eecab6632f064f0caf2698754033a926cd382fb0b6105ebcbb0f85229f7e264f.jpg
while they can pay as low as this much
https://blossom.primal.net/555e6f1a87ac9486c71dce64200c00913cc9b45d5c2ddbf519be4ba4f6f38c36.jpg

2026-05-28 07:16:24 UTC

W milestone soon
https://ocean.xyz/stats/bc1q35dya9dyx3pq6fnq34k75k7vztryy8r9vmzjuz
https://blossom.primal.net/6b857c97314d159f3cde148669c59b83669a4fbb9a75da711da5bfffbce91e50.jpg

2026-05-28 06:29:14 UTC

GM, It's BIP110 SUMMER
so im gonna zap only 110⚡
and gonna mine everyday
https://blossom.primal.net/051ccfb3a06aa92c5eb429e99418b0cb410e7864a26fc756bc6a8d927d6c4bc1.jpg

2026-05-28 06:13:24 UTC

- reply

how to config orbot?

2026-05-28 06:02:57 UTC

- reply

guide
#naddr1qq…tavy

2026-05-28 06:01:59 UTC

- reply

Citrine+Orbot
Citrine is in ZapStore
https://github.com/greenart7c3/Citrine
https://github.com/zapstore/zapstore

2026-05-27 18:52:31 UTC

my nostr relay on my phone always have some clients connected to it. its nice
https://blossom.primal.net/e2738fc6c1242a7b77800b48419bc8fcb66413dec6c40a73ddbe31911164c9e8.jpg

2026-05-27 04:43:29 UTC

GM :)
https://blossom.primal.net/62d09c50e447615217d533ad5f1fbc1cce31262ca97aec2e6f713b0ea1299adc.jpg

2026-05-23 10:30:31 UTC

- reply

imagine the sick plans they had for those 4. and imagine how many many more didn't get caught.

2026-05-22 04:58:03 UTC

2026-05-20 18:43:39 UTC

i knew @nprofile…4e3p was kinda dumb, but didn't know he was this low:
https://youtube.com/watch?v=MnJUC6xLUrY

2026-05-09 05:20:24 UTC

- reply

GM
state isolation is the key
#nevent1q…hzgl

2026-05-09 05:19:59 UTC

- reply

many people don't understand the point of scaling bitcoin.
if the bitcoin user is not running a node verifying their own state, it becomes centralized. bitcoin is decentralized because i verify the state myself.
base layer needs to stay as a global sync layer, final settlement, etc. it should grow slow, and should only include important events that everyone on the globe should know about.
if the timechain gets bigger, people can't run their own nodes anymore. making it centralized. trust based.
the current node impls are already have a terrible ux. hard to run a node, even harder to make it useful. but you still can do it with a old laptop even. which is amazing.
and the second layer should have isolated states. so base layer is a global state that everyone needs to follow, if your second layer creates another global state or chain, its not scaling, its centralizing because you can't run it, its just more data to download and verify globally.
lightning has channels which are isolated from each-other, i don't have to download and verify every lightning channel ever to verify my channel's state. which is correct way to scale, isolation of state.
that's why things like rootstock, liquid, or zkrollups are not really scaling solutions, because they create another global state that you have to download and verify, if you dont wanna trust and verify.
there are better ways but i haven't seen anyone impl them. but basically the state isolation is the key. like with lightning.

2026-05-06 09:56:46 UTC

- reply

when you keep buying bitcoin and it starts pumping before you can't buy more.
*sad* :c

2026-05-06 05:22:44 UTC

GM
seeing ocean mining payout notifications in the morning feels good
https://blossom.primal.net/0de3b6525f89ec34e1c664393a30abae66c0975f858e1833eca33433e690b2ab.jpg

2026-05-05 14:54:26 UTC

- reply

https://ocean.xyz/docs/lightning#blog-bottom_post
if it doesnt help at all, i can help personally.
how i do it is, i have sparrow wallet.
it lets you sign messages using the bitcoin address.
so all you have to do is go to ocean's config page, like this:
https://ocean.xyz/config/bc1q35dya9dyx3pq6fnq34k75k7vztryy8r9vmzjuz
copy the json text, paste it in sparrow wallet message, sign it.
copy the signature.
paste it on ocean.
save.
it requires a BOLT12 lightning offer(reusable invoice).
easiest way is just using coinos's lightning wallet, coinos also let's you auto redirect/transfer balance.
so if you dont wanna keep it on coinos you can redirect it to another lighting wallet from there as well.
sometimes it might fail to do the lightning payment, because cant find a liquid channel, it might fail, sometimes few days in a row but it succeeds eventually. ocean keeps retrying.

2026-05-05 14:40:52 UTC

here my ocean account:
https://ocean.xyz/stats/bc1q35dya9dyx3pq6fnq34k75k7vztryy8r9vmzjuz
i was thinking about keeping it private and stuff but fuck it.

2026-05-03 08:38:44 UTC

ok i have bunch of CDs from pre-2010.
i thought they were dead already at this point, like they are filled with scratches and stuff.
but nope they are working, finding some old videos, images, and also "projects" i was working on in 4-5th grade and stuff lol.
weird feeling.
backing them up.

2026-05-01 09:57:44 UTC

- reply

unless plebs actually start mining.
i mean all you have to do is start, you already get back what you spent.
unless you are bidding with unreasonable expensive prices for some reasons.

2026-05-01 09:37:21 UTC

- reply

still only 2 blocks per period

2026-05-01 09:36:18 UTC

- reply

idk

2026-05-01 09:30:44 UTC

i have a feeling if the hashrate marketplaces keeps maturing, it will also be able to be profitable for the miners renting/buying hashrate as well.
i know matthew says it will not be. but even right now if you place your bids on the profitable side you are still gonna get hashrate time to time, especially if you dont have a restricting speed limit.
i mean i have been thinking, hashers just care about stable predictable income, which selling their hashrate directly provides. and miners that are buying/renting hashrate don't have an electricity bill to pay. so it sounds like there can be a middle ground.

2026-05-01 09:21:35 UTC

GM
Rent at least 50PH/s per day, keep recycling it.
Support a peaceful BIP110 activation.
Make Bitcoin mining desenterlized.
And also put your name and block on the timechain, being a part of the history.
https://blossom.primal.net/e68950dec91edf472c78dfe5db899082a2b663d65abf4bff3ef038d1444d476c.webp

2026-04-26 05:46:45 UTC

- reply

im skeptical of charity organizations.
i believe that money just gets funneled up to the parasites.
teaching people about money, and stop their value bleeding, stop them from being milked is more important.
i believe in one to one charity if you are gonna do it, like help people in your community and stuff. people you know. instead of throwing money at organizations.
also we have parasites gathering money, creating local communities, stealing land, buying countries. and doing all that and more for their sick desires. instead of fighting against them just spreading money so it goes back up to the parasites is not great.
you should use it to form a community physically, teach your community, create a opposition with good intentions against to the parasites. the community should gather more energy, help eachother, and grow. you should form a bigger, smarter community, against them. few thousand bitcoin is nothing. its not a lot. have millions, then spread the few thousand around to support your cause, once you are sure it will most likely be funneled up to you instead.
keep your energy, and keep gathering more, starve the parasites, steal their energy.

2026-04-20 05:20:19 UTC

GM, mining
https://blossom.primal.net/190b3762f2ff525a21c3403a4882f041250b1ca511a6d3ccb467843aa62b683e.jpg

2026-04-19 15:16:30 UTC

everybody is such law cock suckers.
everybody try to benefit from something or get their way.
nobody is thinking if it makes sense.
everybody wants more laws, more regulations.
everybody wants to sue something.

2026-04-19 08:03:50 UTC

- reply

- really? thief has to find my bitcoin utxos somehow, in order to tell if i have money or not? also you are still thinking about kyc, going in and out of fiat. not in bitcoin standard where you get paid in bitcoin and spend bitcoin, also you can buy hashrate with kyc bitcoin and convert it to fresh coinbase outputs as well. also bitcoin is address based not account based, you never use same address twice.
- did i say anything about mining in my post? i said decentralized everyone can run it. you don't trust anyone or vote on anything everyone verifies the reality themselves. because bitcoin is not a democracy.
let me think about issues of monero:
- oh yes, there's no block size limit, only reason it can be run by normal people is because it doesn't have enough volume. if you can't run a node you have to trust someone else, and that would be just paper xmr because you are not verifying it yourself.
- it also has heavy privacy features by default making txs take more space than it should. no matter you want it or not.
- how many hard forks you had? im pretty sure if xmr was big as bitcoin its development would be a lot more easier to get corrupted. imagine if you had same magnitude of users as bitcoin, all the normies, all the news, all the noise, all the corruption and manipulation. it would be so easy.
- randomx is cool, but what if you had same mining volume as bitcoin? huge servers data centers, all mining xmr. would laptop mining still be profitable? it wouldn't be profitable. nothing changed. but bitcoin mining is simple, used as heating in many places, you can rent hashrate from hashers in free market as well mine yourself fresh bitcoins.
so overall it seems only reason monero works right now is lack of adoption and volume. as soon as you have adoption everything breaks, because you like hard forks, you dont have proper limits to keep layer one small and easy sync settlement layer. and soon mining gets bigger your laptop wont be profitable, and you can't buy a 200usd asic either, because you would need a huge rig with cpu and ram and stuff just for mining.
but don't worry, you won't get the volume or the adoption, because monero privacy by default stance is way too obvious, way too scary. its not a good trojan horse. so maybe just use it. don't scream everyone to use it as well. and attack everything else.
do i talk about that i also mine monero on my pcs? i don't. do scream monero? no. because its only useful when its small and niche.

2026-04-18 16:24:23 UTC

burning sats again, to get them back as mining rewards
https://blossom.primal.net/070881efbefcecd8bbbcf24a7d9e84c3f06b01cb85b66c1ab7607ed19f945e6a.png

2026-04-17 21:17:28 UTC

everybody talks about game theory of bitcoin.
nobody talks about the game theory of nostr.
nostr wins eventually because nostr apps might fail or get replaced, but once you are on nostr, you are always on nostr.
and also if you are making an app, its makes more sense to make it on nostr, reach an exists userbase without getting hurt by network effects.

2026-04-17 18:19:44 UTC

- reply

what purpose running multiple nodes serve?

2026-04-17 10:47:42 UTC

- bitcoin is the best performing asset in know history.
- its an amazing money, easy get paid, or pay to people in bitcoin, online or irl. lightning fast.
- you are able to run it actually. its decentralized.
- great way to measure other things you might wanna buy or sell. actually tells you if its worth it or not.
- its stable and very predictable at scale.
- it can scale the right way, with isolated layers. like lightning.
- if you are keep buying it, then it also don't have any short term risks too. its gets averaged out.
why wouldn't you make it your money? are you retarded?
https://blossom.primal.net/9a87086911d9ae237f9d8c291ef6577d005b6e94cb92393fb22f5dfd24f086cb.png

2026-04-17 04:31:38 UTC

GM
https://blossom.primal.net/cd919a3725b726bd31b46295801f4c397225642d5528b7d8f96666d9b1c868ea.jpg

2026-04-16 19:16:55 UTC

tauri is cool btw
https://tauri.app

2026-04-14 08:31:40 UTC

VERY IMPORTANT VIDEO
EVERYONE SHOULD SEE
https://youtu.be/iyx6h3SUgqc

2026-04-13 17:44:46 UTC

Mining with BIP110 https://blossom.primal.net/1faec79ab59a744c90dccaf4a8ef25b90926c3624330afe6b04893bd4f3f6dd6.png

2026-04-12 03:38:10 UTC

- reply

isn't it?

2026-04-11 11:03:52 UTC

masculine argue to adjust braiins hashpower bids

2026-04-09 06:55:42 UTC

GM
https://blossom.primal.net/c2a3e2938b0f8be5b6c060bc578c326bf93409cadf025da21511621e9d880760.jpg

2026-04-08 06:37:12 UTC

- reply

if there is demand supply will appear