Buy crypto anonymously on the Incognito pDEX   

Incognito Whitepaper: Incognito Mode for Cryptonetworks

#25

So where I can find the source code to generate the burning address 15pABFiJVeh9D5uiQEhQX4SVibGGbdAVipQxBdxkmDqAJaoG1EdFKHBrNfs?

1 Like
#26

What I want to state here is that, it is possible that someone (who generated the burning address 15pABFiJVeh9D5uiQEhQX4SVibGGbdAVipQxBdxkmDqAJaoG1EdFKHBrNfs, who knows, right?) knows the corresponding private key. Thus, he/she can spend the coins belonging to this address.

2 Likes
#27

Hi @Semaj,

15pABFiJVeh9D5uiQEhQX4SVibGGbdAVipQxBdxkmDqAJaoG1EdFKHBrNfs
This is the old burning address that generated by this commit.
It’s just a random point on the elliptic curve. So, it returns different results for each execution. We can’t reproduce how to generate this burning address with this code.

Therefore, we upgrade the generation new burning address from the predefined seed as this code.

1 Like
#28

Your concern totally makes sense and your solution is still possible. Basically, we can reject any transaction that used one of the inputs (including both the real one and fake ones) belonging to burning addresses 1 & 2. Because all output sent to the burning address is a no privacy transaction.

3 Likes
#29

The links do not help at all. If the code cannot generate the burning address, who knows if it is randomly chosen or someone just put it there. So basically, as a user, telling me to believe that no one knows the private key is like telling me to stop using blockchains.

1 Like
#30

Did the team implement any mechanism for this?

1 Like
#31

We will add code to reject these transactions that spend inputs from the old burning address.

2 Likes
#32

Hope to get your update soon

1 Like
#33

Have the check finished yet?

#34

We are building the privacy v2 - it’s more privacy and more security. And we will reject these transactions that spend input coins from the burning address in this upgrade version. You can see its process here. Thank you.

2 Likes
#35

Is there any reason that that burn address couldn’t have been 0000000000? I think the community would agree that it would be hard to know the seed of this account. Another option is to take the ASCII for BURNBURNBURN and use the B64 encode for our burn address.

1 Like
#36

easy thing they never thought of