Search results

A quorum participant always knows all the other participants. Actually, the whole network knows all participants of the quorum, as otherwise the individual nodes (including the receiver of the IX) would not be able to verify the votes/locks. So, the attacker could easily identify all his members...

I found some time to re-investigate this issue. The underlying issue is known in Bitcoin, and described in https://github.com/bitcoin/bitcoin/issues/10004 To sum it up: The limitation on maximum number of chained transactions is just one part of the problem. The problem that makes this so bad...

We are working on an on-chain and deterministic masternode system which will allow all DAPI clients (and other SPV type clients) to query and verify a masternode list. This will require an initial (hardcoded or from DNS) list of nodes to be known, which can then be used to query the current...

Thanks. This sounds like what would actually solve the problem (without needing so many split outputs). If sendmany is used to send payments to multiple recipients, the number of unconfirmed ancestors should be reduced dramatically.

You could, or you just set -limitancestorcount to a higher value which would have the same effect. Not sure if it would help however, as other nodes would still reject the TXs. It's possible that your wallet would then queue up more transactions locally and rebroadcast them when new blocks are...

Did you verify that you do not suffer from the same problem as reported by ec1warc1? As UdjinM6 explained, the problem is most likely that too many transactions are sitting unconfirmed in the mempool while you try to send new transactions which spend the unconfirmed transaction outputs. The...

Melde dich am Besten mal im Discord bei mir (heiße dort auch codablock). Ich vermute dass du mir dann Logdateien schicken müsstest oder im ungünstigsten Fall die wallet selber (was wir vermeiden sollten!).

@ec1warc1 Most likely unrelated to your actual problem, but from the log snippets I see that your keypool has ran out of pooled keys since quite some time. That means, if you don't do VERY regular backups atm, you'll loose some (or all?) of your Dash in case you loose your hot wallet. Old...

I don't fully understand your idea, but that's fine ;) You could try out the new "devnets" feature that was just recently merged into our develop branch. The PR and description can be found here: https://github.com/dashpay/dash/pull/1791. More documentation and examples will probably follow...

@GrandMasterDash which OS and version are you using?

The behavior you see is most likely due to an optimization that was recently added and the large blocks that appear on testnet. The optimization (assumed valid block) skips some verification for all blocks which are the ancestors of a known valid block. The feature was backported from Bitcoin...

Just watched it. He is basically right about most of what he talks about. He however misses to mention that most of the attacks he is talking about can also be done on full nodes. All the peer discovery related stuff (DNS, MITM, spoofing, ...) all apply to full nodes as well, so this is not SPV...

Do I understand you correctly that this would require base stations where users would have to connect to so they can send transactions? Unfortunately the forum removes the t= parameter from youtube links. Can you tell me at which time it's about SPV security? Really looking forward to the numbers.

I had the same thought. I could just set him on ignore. But he/she is so massively present in the forum, he makes a very bad impression. He asks critical questions very often, which is perfectly fine. Such things should be asked and people should answer them. But he asks these questions so out...

You didn't even wait for him to actually post a link to what he's referring to :D You could have also done your own homework and googled for it...try it...a hint: "bitstat broadcast".

You shifted the discussion to something off-topic and out of context and now you demand me to answer your question based on that? In the next paragraph you AGAIN shift the discussion to something off-topic. The discussion is not about you, it's not about what you invented before anyone else (and...

Ok, thanks for posting this. I'm answering now not to continue our technical argument, but to showcase your style of argumentation. 1. The discussion was initially about the original topic, BROADCASTING via satellite. I tried to point out that the limitations of this solution would be...

I tried demo, really. But it's hopeless. You throw in completely unrelated stuff, mix up stuff, use stuff out of context. It's completely hopeless. Having technical arguments with you is hopeless. Because you seem to believe you understand what you're talking about, but you're on such a high...

I'm pretty new to this community, only joined a few month ago. When I joined, my first impression of demo was that he/she is just a harmless troll, sometimes simply not getting what a thread is about and thus trolling and hijacking. Well, now I've changed my mind. I've seen too much stuff...

I'm speechless by the level of trolling and hijacking you're currently doing. I really don't know what to say. Also, there is so much wrong with your reasoning that I don't even know where to start...and I know it won't help to even start. And again...wtf? Now explain to me please how your http...