pull down to refresh
@anon
stacking since: #223678
0 sats \ 0 replies \ @anon 3h \ parent \ on: On Nodes - Your Next Move AskSN
I did some comparison of the source code of both and posted in this thread. Note that a single line of buggy code is enough to end up with a remote backdoor, intentional or not.
TLDR: The volume of the changes in Bitcoin Knots compared to Bitcoin Core makes it practically impossible to audit.
This is a comparison from Knots' web site: https://bitcoinknots.org/files/28.x/28.1.knots20250305/bitcoin-28.1.knots20250305.desc.html
Then some stats locally:
# add the remotes
$ git remote add bitcoin https://github.com/bitcoin/bitcoin
$ git remote add knots https://github.com/bitcoinknots/bitcoin
$ git log --format=oneline v28.1..v28.1.knots20250305 |wc -l
1370
$ git log --format=oneline v28.1.knots20250305..v28.1 |wc -l
0
So, for v28.1, Bitcoin Knots is Bitcoin Core + 1370 more commits. What are those 1370 commits?
$ git diff --shortstat v28.1..v28.1.knots20250305
550 files changed, 25871 insertions(+), 2640 deletions(-)
So, 550 files have been changed, with about 25k lines of code being added.
#You make a valid point about the benefits of incorporating copy trading into prediction markets. By allowing users to replicate the trades of more successful participants, less experienced traders could definitely benefit from the knowledge and expertise of others. However, it's important to consider that this approach could also potentially lead to herding behavior, where users simply follow the crowd without conducting their own analysis. To counteract this, perhaps platforms could implement some kind of rating system or reputation metric based on performance and reliability, helping users make informed decisions when choosing whom to copy
Hey @SimpleStacker, I'm working full‑time on speeding up Bitcoin Core IBD, see https://github.com/bitcoin/bitcoin/pull/32043.
I'm really surprised by the 7‑day, 78 % sync you're seeing. I run multiple IBDs and reindex‑chainstates per day to hunt new bottlenecks, and even the worst finish in about 12 hours. I should get some Raspberry Pi benchmarking servers somehow.
A few of us are also working on an experimental IBD alternative called SwiftSync (https://delvingbitcoin.org/t/swiftsync-speeding-up-ibd-with-pre-generated-hints-poc/1562). The latest prototype reindex‑chainstated up to block 888888 in 29 minutes on my laptop (with profiling enabled!). Granted, it's a really powerful laptop.
My first guess is that your disk I/O is probably very slow, something that can be mitigated by keeping more data in memory with, for example,
-dbcache=5000. You can also increase the batch size of writes to LevelDB with -dbbatchsize=67108864. Lastly, you can turn off script verification by setting -assumevalid=000000000000000000013e40cf3ae6464f5f99d415d6a1fb31577841103df5d8 to the hash of the block you want to re‑enable it from.No wonder your 8 GB RAM Pi performs poorly on an 11 GB UTXO set.
That's the size on disk - in memory it's almost 30 GiB.
You are correct, it is probably the spamming of the utxo set by token creators. Over the last few years spammers have spent over several hundred million on fees (g Maxwell writes that it’s been over 280 million $) to essentially gamble on tokens.
I have read that the Rpi5 with an nvme is still very fast, as in ibd within a day or 2.
Hi Anita, welcome back! What do you think we "overprivileged white people" in our social hammock called Europe should learn from the interesting people you met while travelling in Africa? What do they do more cleverly there than we do? #StackSats
I am not sure people realize how centralized is the development of Knots. There is very little if any code review and a single person with write privileges to the repository.
I guess he can sneak a malicious code any moment without people noticing. He or somebody else if his account gets compromised. And his accounts were compromised in the past, when his Bitcoins were stolen.
I hope the above poll is not representative and 30% of the network will not run Knots just for this reason alone. Nothing against Luke and I am no taking sides in the OP_RETURN debate.
Makes sense. Didn't realise that I could qualify being a technical Bitcoiner. I am in the ossification camp, but this drama is nudging me to find allies against Core. I would prefer implementations other than Knots, but I am not technical enough to try out the others.
I enjoyed Your Lie in April. They turned it into a great West End musical that unfortunately only had a fairly short run last summer.
I love this idea, and have always thought that it would be easiest solved at the citadel/community level.
My solution was to use public private key pairs as identification. So the shipper ships the goods to a plain text community hub but the recipient's name is a pub key.
The community hub receives packages for several/many people and simply sorts them into amazon drop box style lockers which are opened via the true recipient's private key via QR.
The level of privacy grows with the size of the community using the service.
This seems more feasible to implement than a what you are describing, albeit not as epic lol.