Topic: [ANN][AC]AsiaCoin - Relaunch - page 52. (Read 400999 times)

I'm one of the AsiaCoin bagholders. If the dev does not come back with version #2, then we will have to come up with solutions to fix this.

I'm going to start adding names to this list who are bagholders that want this fixed. I'll start with my name.

AsiaCoin Bagholders who wants to see a fix:

CryptoSteam
Nicolaas.R
silencesilence
bluebit25
WildChaser777
istop08
GröBkAz
Maxikosw (Maxikose on freenode irc)
hrt
cjp007
kache
minuchi.str
amit2007gunjan
noobthegreat
EEKman (Lost 3K USD. I feel you. I lost tons myself)
Maestro1
Xuorc
probrian
artem6662
Shkembe
Wolden
probrian
bittcoinn
voisina


And see what TokyoGhetto said:

If I were to put a price to it.. (and note: I'm still not signing up for it).

I think it would be fair to place a 10 BTC bounty on an effort that would preserve the existing "network".  

This is a much bigger job than the WC folks.. it requires some surgical scripts to be created.

But if those 3 billion coins are moving on the blockchain, then I don't think, anyone can save anything now. Is there a running block explorer for the coin and is address of 3 billion coins known?

I would do the MintPal freeze as they are the first to do it before Cryptsy.

As with everything in cryptos.. it's just all based on distributed agreement.  So yeah.. it's really just about picking an arbitrary block,and agreeing that is the block to freeze at.  But we already have 2 candidates: cryptsy drop, or future.. so it's really about being able to come to a consensus..

if you are a gun-for-hire, what is your price?

I am.. I've created 3 coins successfully, in 2 cases it was to help an existing community that got scammed and/or had failed launches.  Checkout Realstackcoin and GPUC.

But unfortunately.. doing so isn't very profitable for my time and effort.. apparently if you are not scamming its kind of hard to make money creating coins  

Also i've found through previous experience that all this is for not, unless you have a serious and huge marketing leadership (with also money to invest).. able to convince the broader ecosystem (exchanges, blog writers), that this can be resurrected.. it's going to be hard even if a developer fixes the blockchain.

Can we just pick a block in the very near future and declare it in this forum as the block we will reset from?  Or do we need to do something else?

And another thing.. the clock is ticking on this.. in order to save/preserve blockchain you need to freeze blockchain, that is: agree on a certian block N, after a certain block, all transactions are invalid until the fixed wallet and/or blockchain is rereleased.

Otherwise the premine is still working its way through the network, as we speak.. The network is still live right now.  So the "bad" premine is making its way through to new accounts I'm sure, making it incrementally harder to repair it.

after the date and time of dropping cryptsy can easily eliminate residual blocks

+1. Are you a coder? If so, it would be awesome if you can help fix this. There is a huge community here bagholding.

And another thing.. the clock is ticking on this.. in order to save/preserve blockchain you need to freeze blockchain, that is: agree on a certian block N, after a certain block, all transactions are invalid until the fixed wallet and/or blockchain is rereleased.

Otherwise the premine is still working its way through the network, as we speak.. The network is still live right now.  So the "bad" premine is making its way through to new accounts I'm sure, making it incrementally harder to repair it.

And another thing.. the clock is ticking on this.. in order to save/preserve blockchain you need to freeze blockchain, that is: agree on a certian block N, after a certain block, all transactions are invalid until the fixed wallet and/or blockchain is rereleased.

Otherwise the premine is still working its way through the network, as we speak.. The network is still live right now.  So the "bad" premine is making its way through to new accounts I'm sure, making it incrementally harder to repair it.

I'm one of the AsiaCoin bagholders. If the dev does not come back with

version #2, then we will have to come up with solutions to fix this.

I'm going to start adding names to this list who are bagholders that

want this fixed. I'll start with my name.

AsiaCoin Bagholders who wants to see a fix:

CryptoSteam
Nicolaas.R
silencesilence
bluebit25
WildChaser777
istop08
GröBkAz
Maxikosw (Maxikose on freenode irc)
hrt
cjp007
kache
minuchi.str
amit2007gunjan
noobthegreat
EEKman (Lost 3K USD. I feel you. I lost tons myself)
Maestro1
Xuorc
probrian
artem6662
Shkembe
Wolden
probrian
bittcoinn
voisina
jarserk
dirtypolecat
masterboy
nin7672
syrota
AC2 (1.35 million AsiaCoin)


And see what TokyoGhetto said:

with the amount of people involved...it will be worth it. Rising like a phoenix from the ashes will actually generate more interest in the coin, people will be amazed at how communities can rally together in the face of adversity.

The exchanges will not ignore us, the amount of trading volume this coin brings is INSANE. We need to restore confidence. We will adapt and overcome.

Copying the blockchain would still require surgical removal of the premine transactions all the way through the blockchain.  So you have to do that work anyways.  At which point, there's no point in a new coin, unless it's just for a "rebrand".

Anyways I see 2 methods of fixing it:

  1) Allows use existing wallet.dat and db:
    - a) Pick a current block N, freeze things at that block (meaning any transactions after that is technically invalid)
    - b) Walk through blockchain from the beginning and trace the premine transactions all the way to current block N.
    - c) Find all addresses that have coins that originated from original premine transaction.
    - d) Hard code in the wallet file transaction accept code to BLOCK those addresses from allowing to send those transactions, greater than the amount of the bad "premine".
    - e) Compile, Release new wallet.

    - PRO: you don't have to delete your wallet.dat or db
    - CON: going to be some huge IF statements in the code somewhere..

  2) Allows use of existing wallet.dat (but throw away old db):
    - d) Do the same as above, except deviate from step d)
    - e) Derive a new list of addresses and their "real" coin amounts at block N
    - f) Code in the genesis block of a new chain, a distribution of those coins from this list.
    - g) Compile, Release new wallet.

    - PRO: more streamlined blockchain/db
    - CON: you need to force all users to delete their DB but NOT their wallet.dat (may be some confusion here).

Copying the blockchain would still require surgical removal of the premine transactions all the way through the blockchain.  So you have to do that work anyways.  At which point, there's no point in a new coin, unless it's just for a "rebrand".

Anyways I see 2 methods of fixing it:

  1) Allows use existing wallet.dat and db:
    - a) Pick a current block N, freeze things at that block (meaning any transactions after that is technically invalid)
    - b) Walk through blockchain from the beginning and trace the premine transactions all the way to current block N.
    - c) Find all addresses that have coins that originated from original premine transaction.
    - d) Hard code in the wallet file transaction accept code to BLOCK those addresses from allowing to send those transactions, greater than the amount of the bad "premine".
    - e) Compile, Release new wallet.

    - PRO: you don't have to delete your wallet.dat or db
    - CON: going to be some huge IF statements in the code somewhere..

  2) Allows use of existing wallet.dat (but throw away old db):
    - d) Do the same as above, except deviate from step d)
    - e) Derive a new list of addresses and their "real" coin amounts at block N
    - f) Code in the genesis block of a new chain, a distribution of those coins from this list.
    - g) Compile, Release new wallet.

    - PRO: more streamlined blockchain/db
    - CON: you need to force all users to delete their DB but NOT their wallet.dat (may be some confusion here).