Bitcoin Forum
March 08, 2021, 10:13:29 AM *
News: Latest Bitcoin Core release: 0.21.0 [Torrent]
  Home Help Search Login Register More  
  Show Posts
Pages: [1]
1  Other / Archival / Re: Beware ZCOIN (XZC) Lelantus concept scam on: October 09, 2020, 02:16:16 AM
Dude, this is straight-up wrong, here's a direct link to the Lelantus branch on Github.

It takes 2-minutes to google this stuff, and maybe 40 minutes to self-compile and play with it. Additionally, there is already an existing privacy protocol in the interim, Sigma. Which has not only been in production for a year + but also has been referenced by other projects. The current Zcoin wallets have Sigma, which is something you can directly test and Lelantus is available for testing on testnet

I personally have worked with both Sigma and Lelantus as my developers have contributed to the Zcoin codebase while working on stealth addresses for their project.
2  Other / Bitcoin Wiki / Re: Request edit privileges here on: May 11, 2020, 07:12:45 AM
Hi Guys,
My username on the Bitcoin Wiki is HysMagus
3  Bitcoin / Development & Technical Discussion / What are some decentralized/better alternatives to DNS Seeds? on: January 15, 2020, 05:33:45 PM
I'm doing some research into DNS Seeding, and alternative options to it. My main thought process is that, even if DNS Seeders are a functional but imperfect solution for initial peer discovery, they do still but a long term burden on the few individuals that are running the dns seeds, and do have a slight centralization factor. Additionally, the fall back of chainparams seeds generated using the included python script can fall out of date quickly, and requires house-keeping/pruning of dead peers . I've tried searching to see if anyone was already working on better options or improvements to the existing solutions, but I haven't had much luck.

For reference:
DNS Seeding is visible in the code here  and defined here with the codebase for the seeders (by Sipa), available here

 Chainparams peers that are hardcoded as a fallback to dnsseeds defined here and visible in the codebase here
4  Bitcoin / Development & Technical Discussion / Re: What is an appropriate reaction to dealing with Well-Poisoning Attacks on: August 16, 2019, 04:05:15 PM
Otherwise, you should hope there's law such as Section 230 of the Communications Act and Section 512 of the Digital Millennium Copyright which protect you.
See Why Porn on the Blockchain Won't Doom Bitcoin for more info.
Awesome Link! This solves part of what I was looking into, I was hoping someone had a technical solution of some sort but I don't think that's the case in this scenario

Did Bitcoin lose reliability of what it was intended to be? No.

I believe this topic should be in the legal sub.
I was hoping there were some technical solutions we could look into, but I don't think that's the case after further research. Also to clarify my prior point, I wasn't trying to say having illicit content on the Bitcoin Blockchain would hamper reliability, but rather the act of rolling back the chain in order to remove said content would hamper reliability. Sorry for the miscommunication!

This is the price we have to pay for using an immutable technology. Yes, authorities and regulators will have a field day with this and we do not even talk about the media frenzy that would happen, if they get wind of that.  Tongue 

If we start cherry picking to remove specific transactions from the Blockchain, then we will destroy one of the "best" features of this technology. I think the best comparison would be to say that people would require shutting down the Internet, because it is being used for illegal activities. You cannot destroy a technology that brings so much positive things to this world, because a small portion of the world are using it for illegal activities.  Tongue

DO NOT throw out the baby with the bath water.  Roll Eyes
Absolutely, even attempting to create the ability to effect immutability would invalidate one of the key foundational points of bitcoin! Going on your point of both Authorities and Media having a field day with this issue. This could be the perfect media-focused attack against bitcoin if a coordinated effort was done to further attack the image of cryptocurrency.

5  Bitcoin / Development & Technical Discussion / What is an appropriate reaction to dealing with Well-Poisoning Attacks on: August 16, 2019, 04:42:28 AM
Hi All!

I've been having this problem chew around in my head for a while, and have been thinking of potential reactions in regards to dealing with it. I haven't been able to come up with any solutions, so I wanted to see if the internet had any ideas.

Problem Context:
Two individual network users on the Bitcoin Network exist on the same chain, Alice & Bob.

Alice is a full node on the network, keeping a copy of the full chain, doing her part to keep the chain decentralized.

Bob is a bad actor, who wants to negatively impact Alice and the rest of the honest individuals in the network using the cheapest and most expedient way.

To do this, Bob takes advantage of the functionality available on the chain currently to append data to a transaction. In doing so, he attaches illicit content to be uploaded to the chain, something that is almost universally illegal, such as child pornography or revenge porn.

Using a service like crypto graffiti (, which is functional on forks of Bitcoin, as well as the reference implementation/main chain itself or by uploading a string of 40-80KB increments, Bob, a sufficiently motivated attacker can upload content to the chain at a reasonably affordable cost.

Now, if Bob's transactions are successful, Alice and the rest of the honest network, are now hosting content that could be considered legally dubious in their home jurisdictions. Of course, that's not to get into the moral implications of hosting said content.

Now at this point in time, the damage is done, this data cannot be easily removed, as for Bitcoin to retain the respect, trust and censorship resistance (of transactions) that it has, the chain cannot reorganize. At the same time, even if there is a will by a large number of users, it would be economically and financially unfeasible, as if the offending transactions were not detected fast enough, they could be past the natural reorganization window.

Problem Statement:
If all of the above is true, as an honest node, miner or general user of bitcoin, what should the course of action be? Additionally, with any course of action what are the long-ranging implications of having the well poisoned so to speak?

Personal Opinion:
While I may have interjected my personal opinion a bit in the last paragraph of the problem statement, stating that the network cannot be easily changed for it to retain the trust and reliability that it has. I'm at a loss on the appropriate path on how to properly react to something of this nature.

What are y'all's thoughts?
6  Other / Off-topic / Re: GitHub is shitty, why not a decentralized solution? on: August 16, 2019, 04:13:08 AM
There is an existing decentralized git platform* setup on ZeroNet, it's a little clunky but it's usable enough to be a censorship-resistant route to share code.
You can find a link to it on the ZeroNet site directory.

* edit to clarify a platform exists, not a clone of any specific codebase or any work done by specific parties.
7  Bitcoin / Bitcoin Discussion / Re: What your family thinks about that you into crypto on: August 16, 2019, 03:59:16 AM
For the most part, my family has been supportive, outside of one cousin who sat me down and explained to be how Bitcoin was a dangerous ponzi and that I should listen to the founder of the bank he works for and dump all my crypto and move into safer investments, like strip malls.
8  Bitcoin / Development & Technical Discussion / Re: Thoughts on this private key stealing mystery on: March 25, 2018, 06:43:16 PM
From the digging the user /u/n0mdep did on reddit, it appears to be an old PHP library issue, wallets using this library may be a possible source. One of the addresses ("1JCuJXsP6PaVrGBk3uv7DecRC27GGkwFwE") is mentioned in a 2017 PHP bitcoin shopping cart issue.
Pages: [1]
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!