Knots:

Reply to this note

Please Login to reply.

Discussion

We Will win this!

Number go up!

#knotstr will win this battle

Would comment but core says i'm not qualified. i run nodes. but not qualified. 🤔

I'm just a filthy HVAC tech in my basement. Running Knots. Watching this issue with intensity.

I tend to flip over to Clark Moody Dashboard .... he doesn't seem to update as quickly.

i think his script runs every 2 weeks

99.9% will still be useless!

Because bitcoin is meritocracy, not democracy!

And bitcoin is bitcoin core!

😪🤣

Less is better than more spam

I have my node set to drop knots peers so my Ashigaru coinjoins don't get filtered out by my node peers.

The joins should be fine, it's the needlessly large OP_RETURN that's getting your stuff rejected from Knots mempools (rightly so, we're not obligated to store placeholder metadata about your coinjoins).

You aren't the one who gets to decide that my privacy is "needlessly" large when it is within long term consensus.

>placeholder

it isn't even doing anything.

i mean if it was actually used for something... but this placeholder thing is just retarded.

RIght, I think they only use ~32 bytes which Knots permits by default. They "reserved the right" to use 45 or something - as if you can reserve the right to use other people's computers.

What the fuck, they're not even using it? Conflict grifters. I think they might even be being used by agents of the banking cartel, frankly. Controlled opposition. We're talking Whirlpool, right?

palantir is who is behind it btw. i'm sure they have jpm and consensys in the operation too.

Explain this perfectly pure transaction form you seek to permit?

Damn right we're not obligated!

I'd like to point out my Knots nodes are allowing slightly longer OP_RETURNs than the default. Filtering out all Knots nodes is a naive approach. Don't accept their false premise that everyone running Knots is running the same policy settings.

What would be the critical mass of Knots nodes, to put pressure on the miner running core v30 not to allow illicit content uploads, as the confirmation might take too long?

That pressure exists regardless. The more we relay it independently of them, the more plausible deniability they have that's all.

MARA will put junk in the chain that is relayed by <1% of the network currently so that isn't the factor at play here for the most part.

Delayed block propagation isn't really significant enough for miners to care. MARA did with the sub 1s/vb stuff but that's the world's least lucrative spam, and they seem to keep dipping into it anyway.

We need more people 'using Bitcoin' which for the life of me I can't understand why we don't have.

Over 90%

Hmm, not sure if this can be achieved in the remaining time. 🫤 I don’t understand why Bitcoin organisation like blockstream, river are in favour of core v30.

this might be a noob comment but that’s just for the publicity accessible nodes right? no telling how many run it non-discoverable right?

No one knows. nostr:npub1ry930jxmrdtzvqfdrq7846ymzcc0hh0ll68ttvjg7kkrptsa0pds3vqy4m had stats that attempted to track non-listening but no one really agrees on how best to do it.

Wrong Luke, sorry.

How would you track a non-listening node isn’t that the point that they are not discoverable?

Right but there are ways to make estimates anyway.

sounds like a fun rabbit hole to go learn about this week. this is why i love nostr always learning new things!

Does anyone know how to point Knots to the full blockchain history that my core 29 is running on? I'd like to now make Knots the only variant on my umbrel. Tks

When you first open knots, it prompts you to select the drive and directory for the blockchain. Just navigate to where bitcoin core saved the blockchain and select that in knots.

Right on 👍🏽 4444

I'm one of them! 😎

This is impressive tbh. Seeing this progress all the way from 9% the last time I paid any attention to this on twitter.

4X4

4444 nodes that cant use lightning, coinjoin, anchor outputs, or package relay. pooring one out for you guys.

Just spreading FUD or you actually think Knots doesn't work exactly the same as Core wrt all that stuff?

No reply as usual

what are you talking about, iv'e got lightning and conjoin working fine with mine, has been for years, never heard of the other 2.

Notice how the majority of spam supporters don't know anything about Bitcoin?

I know that to filter a TX you have to download it first. 🤯

LFG! I’d love to see all the spam heads post their personal email addresses and turn off their email filters. It’s all valid, right. Just ones and zero’s.

Do you know anything about installing Knots on a Raspiblitz? Could you point me in the direction of a good guide?

Yes paul lamb on youtube has a great video for this

Perfect. Thank you.

If you need more help after that don’t hesitate to ask!

Hi Leo,I have error on Start9 with Knots 29:failed to open database path....builds does not support Berkeley DB database format

When I disable wallet then all is ok.

Now the v29 disappeared from your GitHub and so I downgraded back to v28 .

Yes the version with bdb is coming soon!

I installed before verified and imported your gpg key 🔐,all is ok,only minor issue is the version attention from electrum.

Thank you!

Installed after*😂

What was the issue?

Incorrect version,me pool will not work as expected

Mempool dependencies for knots max 29.0.0 and knots is 29.1.0

Oh yeah can’t do much about that, they need to update their package.

But anyway mempool should work normally.

Yes,all is ok

Or maybe is time to push your mempool.guide to start9

I didn’t think of the dependency version, it will also warn about the knots version but you can safely ignore.

I will fix it next release.

https://github.com/Retropex/mempool-startos/blob/044954befae7fd972d20e989e1a09d23fbae2138/manifest.yaml#L65

no,my ideea is to have your mempool.guide in S9 too

Yeah that what it does. 😅

I’m just telling you that if you run mempool guide with knots 29.1 start9 will complain but you can safely ignore this.

Enjoy! 🧡

maybe this help

from logs:ERROR: Indexer failed, trying again in 10 seconds. Reason: Cannot fetch coinbase tx xxxxxxxxx...... Reason: The value of "offset" is out of range. It must be >= 0 and <= 86. Received 90

nostr:npub1ywjjp4dup38veklgw44p2d24n9yze8e4u4gpxwm49ka6rjvyu9dsfg6ejf can help!

At what point does knots become the reference implementation? when mining pools are using it?

Progress 🫡

Damn, making ground! 👍

My blown, that so many ppl trust in a 1mamn dev team, that is bible brainwashed..

It's not one man, this was the lie from two weeks ago.

You just eat the lies and lopp’s slop with both hands, huh? I mean you think the bible is brainwashing afterall, so shouldn’t be surprised.

I recommend you do some research into the bible if you can make a comment like that.

Also, I believe there are a lot more devs than 1 contributing to knots.

It's important that we have decentralized node implementations too.

Someome with "Pet Rock Maximalist" criticising the bible lol.

*facepalm*

omg vegan too

not surprised

Thats actually a pretty impressive number....... that I expect will only continue to grow over time.

Everything will be tokenized.

Actions have consequences.

What percentage of the network runs the latest version of bitcoin core?

How do I check ?

this is the clarkmoody dashboard nostr:npub15n94rarp3n7dz6edx9cugeshn0kcuxtugwu9nzprkpx7yekw7ygqplqru4

love to see it