Pages:
Author

Topic: [SSD] Sonic - 1st TOR with functional anon send - Steganography based Anon App - page 95. (Read 284877 times)

sr. member
Activity: 336
Merit: 250
C-CEX is a scam. I've heard numerous times to trade with caution and here we are again.

This is the SONIC thread, please move your scam comments to the right thread.
Dev, next time you release something, can you put down a date and a country? Cause a lot of us where past the 23rd when you released your app. That created some confusion.
full member
Activity: 182
Merit: 100
So LESS coins exist now?
no, everyone's just mad that their coins doubled.
hero member
Activity: 742
Merit: 500
C-CEX is a scam. I've heard numerous times to trade with caution and here we are again.

Some people never learn.
legendary
Activity: 1148
Merit: 1000
So LESS coins exist now?

I don't think so... Unfortunately... Users will just be reign used at less than 1/4 value for c-cex's screw up.
hero member
Activity: 742
Merit: 500
After migration and salvaging wallet, it returned the same addresses, presumably in the same order, my bet that's bug is related to key pool queue, it's developer job to determinate exact cause, I'm not going to look through every step to find exact line of code which cause this. My time isn't free and I'm not going to waste it on this, thanks. If someone has better explanation why it was happened and why addresses were reused, you can post your version of events.

Address generation is deterministic on purpose. That is a feature added to BTC wallets long ago. If you generate address #X from a new private key, it will always be the same address.

Holy smokes, dude. If you are going to review something, know your business.

[edit]

This is how you can take an old backup of a wallet and recover new transactions that produce their own change addresses.


sr. member
Activity: 326
Merit: 250
SHPING Presale:22-31 JAN / Crowdsale:22 FEB-23 MAR
I feel sorry for the person who lose The best coins ever, but we had also problem in the first weeks of xst one guy lose 150k xst by a  another way.... something with a wallet that i not discuss. I help him to give some coins. So i give also 1000 ssd to that person wo lose a lot on c-cex. Why because i like this coin. I help only one person i know wo it is... But help me wo i will give 1000 ssd....


Sorry for my Englisch
member
Activity: 98
Merit: 10
C-CEX is a scam. I've heard numerous times to trade with caution and here we are again.
member
Activity: 105
Merit: 10
So LESS coins exist now?
legendary
Activity: 1148
Merit: 1000
http://pastebin.com/TDy4WQ5P

for your enjoyment. Every Correspondence between C-Cex and I. I can screenshot any part if you don't believe it.


Got em arg! Not to mention staking customer coins! Lol wouldn't expect anything less from them....
full member
Activity: 182
Merit: 100

You are full of shit. Try again.

Code:
14:23:30
getnewaddress
14:23:30
scjDCfCAFwhPh5CrrntZM4n2irM3EXmKWp
14:23:32
getnewaddress
14:23:32
seF4pdfCKwH4kppNnJowbuRSh3ZkH34FAX
14:23:36
getnewaddress 'account'
14:23:36
sRFS3cT1qmAYtsVg5miGaQia6skRJjdZA9
14:23:39
getnewaddress 'account2'
14:23:39
saYKAi5SgvwZvWJDSVqavarBpzHs8QwYj5
14:27:13
getnewaddress 'account2'
14:27:13
shFxZ2D7dpULoos2bd9BU7TZ7yUfzLkEV6


Your example is not relevant to the case.

Wallet after migration returned addresses that were used before migration, for example:
sc7zK5PrZUbTTfM2ZKrQ3Q6rnxmLtDr858
scSHt3SGSVFuZP6aBP5UiUzYHfWBy5hu7a

After migration and salvaging wallet, it returned the same addresses, presumably in the same order, my bet that's bug is related to key pool queue, it's developer job to determinate exact cause. If someone has better explanation why it was happened and why addresses were reused, you can post your version of events.
OK, fucking c-cex everyone that knows anything about cryptos knows that your exchange is shit, and this isn't the first time you have been accused of stealing peoples coins. No one is going to believe anything you say because there has been countless claims of you stealing costumers coins in the past (and deleting their accounts to try to cover it up).
sr. member
Activity: 658
Merit: 257
★Bitvest.io★ Play Plinko or Invest!

You are full of shit. Try again.

Code:
14:23:30
getnewaddress
14:23:30
scjDCfCAFwhPh5CrrntZM4n2irM3EXmKWp
14:23:32
getnewaddress
14:23:32
seF4pdfCKwH4kppNnJowbuRSh3ZkH34FAX
14:23:36
getnewaddress 'account'
14:23:36
sRFS3cT1qmAYtsVg5miGaQia6skRJjdZA9
14:23:39
getnewaddress 'account2'
14:23:39
saYKAi5SgvwZvWJDSVqavarBpzHs8QwYj5
14:27:13
getnewaddress 'account2'
14:27:13
shFxZ2D7dpULoos2bd9BU7TZ7yUfzLkEV6


Your example is not relevant to the case.

Wallet after migration returned addresses that were used before migration, for example:
sc7zK5PrZUbTTfM2ZKrQ3Q6rnxmLtDr858
scSHt3SGSVFuZP6aBP5UiUzYHfWBy5hu7a

After migration and salvaging wallet, it returned the same addresses, presumably in the same order, my bet that's bug is related to key pool queue, it's developer job to determinate exact cause. If someone has better explanation why it was happened and why addresses were reused, you can post your version of events.

Also if you find a bug feel free to post it, I will gladly admit if I am wrong and fix it.

I think I know what would have happened though.

As you can see in the pastebin the wallet was corrupted and the most recent backup they had was 8 days prior. When reverting to this backup the keypool was taken back to the previous state. This would allow addresses that had already been assigned to be reassigned.
ExD
member
Activity: 107
Merit: 10

You are full of shit. Try again.

Code:
14:23:30
getnewaddress
14:23:30
scjDCfCAFwhPh5CrrntZM4n2irM3EXmKWp
14:23:32
getnewaddress
14:23:32
seF4pdfCKwH4kppNnJowbuRSh3ZkH34FAX
14:23:36
getnewaddress 'account'
14:23:36
sRFS3cT1qmAYtsVg5miGaQia6skRJjdZA9
14:23:39
getnewaddress 'account2'
14:23:39
saYKAi5SgvwZvWJDSVqavarBpzHs8QwYj5
14:27:13
getnewaddress 'account2'
14:27:13
shFxZ2D7dpULoos2bd9BU7TZ7yUfzLkEV6


Your example is not relevant to the case.

Wallet after migration returned addresses that were used before migration, for example:
sc7zK5PrZUbTTfM2ZKrQ3Q6rnxmLtDr858
scSHt3SGSVFuZP6aBP5UiUzYHfWBy5hu7a

After migration and salvaging wallet, it returned the same addresses, presumably in the same order, my bet that's bug is related to key pool queue, it's developer job to determinate exact cause, I'm not going to look through every step to find exact line of code which cause this. My time isn't free and I'm not going to waste it on this, thanks. If someone has better explanation why it was happened and why addresses were reused, you can post your version of events.
legendary
Activity: 1876
Merit: 1005
http://pastebin.com/TDy4WQ5P

for your enjoyment. Every Correspondence between C-Cex and I. I can screenshot any part if you don't believe it.

After having a look at the chat between both of you (Dev and c-cex) everything is very clear the fault is of that from C-Cex as he showed greed too in mode of staking. He is (C-cex)that the responsible for this loss.
legendary
Activity: 1148
Merit: 1000
What's the coin count that was double spent and perma lost?...  Value of SSD should be going up!!!  Less coins in circulation...
member
Activity: 84
Merit: 10
Still getting this error for line 557 and cant compile on linux.

/root/Sonicscrewdriver/src/rpcrawtransaction.cpp:557: undefined reference to `decryptsonictxt(std::basic_string, std::allocator >, std::basic_string, std::allocator >, std::vector, std::allocator >, std::allocator, std::allocator > > >&)'
collect2: ld returned 1 exit status
make: *** [Sonicd] Error 1


Dev, can you please address this call in rpcrawtransaction.cpp so that I can compile your wallet.   

That is because the make file is not fully setup yet. its still missing headers.

OK, well when it's done, I'll open up a blackjack game here for sonic.
sr. member
Activity: 658
Merit: 257
★Bitvest.io★ Play Plinko or Invest!


Also if you find a bug feel free to post it, I will gladly admit if I am wrong and fix it.

sr. member
Activity: 658
Merit: 257
★Bitvest.io★ Play Plinko or Invest!
Still getting this error for line 557 and cant compile on linux.

/root/Sonicscrewdriver/src/rpcrawtransaction.cpp:557: undefined reference to `decryptsonictxt(std::basic_string, std::allocator >, std::basic_string, std::allocator >, std::vector, std::allocator >, std::allocator, std::allocator > > >&)'
collect2: ld returned 1 exit status
make: *** [Sonicd] Error 1


Dev, can you please address this call in rpcrawtransaction.cpp so that I can compile your wallet.   

That is because the make file is not fully setup yet. its still missing headers.
member
Activity: 84
Merit: 10
Still getting this error for line 557 and cant compile on linux.

/root/Sonicscrewdriver/src/rpcrawtransaction.cpp:557: undefined reference to `decryptsonictxt(std::basic_string, std::allocator >, std::basic_string, std::allocator >, std::vector, std::allocator >, std::allocator, std::allocator > > >&)'
collect2: ld returned 1 exit status
make: *** [Sonicd] Error 1


Dev, can you please address this call in rpcrawtransaction.cpp so that I can compile your wallet.   
sr. member
Activity: 658
Merit: 257
★Bitvest.io★ Play Plinko or Invest!
http://pastebin.com/TDy4WQ5P

for your enjoyment. Every Correspondence between C-Cex and I. I can screenshot any part if you don't believe it.
full member
Activity: 201
Merit: 100
stealthcoin.com
Pages:
Jump to: