Quote from: theprofileth on September 23, 2014, 11:03:58 PM

Quote from: barwizi on September 23, 2014, 10:47:39 PM

Quote from: theprofileth on September 23, 2014, 10:26:40 PM

Quote from: barwizi on September 23, 2014, 10:15:41 PM

Quote from: theprofileth on September 23, 2014, 07:08:59 PM

How does having people import their private key make it any easier to calculate the coins due to them? The coins due for each account should be calculated when the snapshot occurs and doesn't require user input so I don't see why a script that securely enables users to provide evidence of ownership and provide an address to receive their coins is any different. You still need to calculate the coins that are due to each account either way. Infact it would be easier to not store every address on your chain and instead have a script that looks at your snapshot data when they go to claim their coins and then sends the correct allocated amount from a pool of redemption coins that is entirely automated removing trust altogether from the system. Plus this way you could keep the redemption system going for far longer and if you wanted have it send you 1% to your address which can be documented on the blockchain this way

I think you need to read all the posts I've made in this regard and the ones on the page and the last from various groups that have already used the same method.

You keep hopping from one area to another

Find a method since you seem to believe there is one that meets the following criteria :

1) Static balances for all addresses in each and every chain (should be scalable to 200 or 400 coins)
2) Easy proof of ownership and redeeming without any need for technical input, just a few instructions
3) Method of redeeming should be scalable up to 200 or 400 coins
4) Balances should be easily verifiable from block 1
5) anyone can redeem offline, and maintain their privacy

Explain to me how what I proposed is not applicable to every single point you mentioned because I seem to be the only one laying out any sort of comprehensive solution. Or better yet explain how your solution fits your own criteria because last time I checked you need to be online in order to sync your wallet that you redeemed

signing a message prove ownership on chain A, and we want to redeem on chain B so you want me to write a script that sends coins to chain B when chain A signs a message?

here is problem number 1 , this means i have to mine all the coins in advance leaving them in my possession, which means i have to take responsibilty for them NO, I REFUSE. not only is it extra work it means anyone who fails to redeem their coins will begin bothering me about it. And considering the sheer number of possible addresses, that will take the rest of my life.

2) your method is highly inefficient and requires that there be a server that automatically pays out, meaning if someone gains access or plain just DDoS it then redeeming is messed up.

3) Your method requires that i remain on hand and become a help desk for everyone yet a simple do it yourself method that is proven exists

4) Your method requires that users be online to redeem their coins, mine doesn't

5) Your method is NOT scalable at all as it requires running every single client of every coin involved

6) in your method balances are not easily verifiable from Block 1

Let me explain How my method trumps yours

1) Once you download the wallet, even if it syncs just the first block, your balance will appear that instant and you are free to move it if you wish.

2) There is no need for proof of ownership, you just redeem your coins and go about your business and even the most technically inept can follow two lines of instructions.

3) It is easily scalable, i already have + 30 Block chain with up to date balances, running a script for a few seconds will compile all the balances and format them ready for inclusion, and if the code is ready, even the genesis block will be mined without any intervention from me.

4) A brand new wallet will reflect your balance

5) you can redeem offline by simply having a copy of the client, no hassle, all security issues got out the window.

Ok so are you saying that your blockchain will contain an address for ever single address in every blockchain we can import from? Also point 5 your solution requires that you get the private key from the client which also needs to be running in order to get it. Also if you plan to not control the horde of coins then how will you claim any unclaimed coins? If you can access unclaimed coins from accounts then you could just as easily claim coins from activated accounts. Also how is signing a message any less complicated than dumping a private key? Your point about being online is invalid as it doesn't matter if you are offline when you redeemed because you can't do anything with offline coins so you will have to go online to effectively redeem them. You are correct that the weakness of my system is that you need an online server but it could be feasible to build the system into the actual network.

You clearly dont get my explanation. I think you should pick a coin that you may hold and set aside a few coins in a separate address, a few days from now the source code will be opened for review then i can throw you a test client where you can see how very simple abnd straight forward it is. The concept of proving ownership and the ability to redeem in a trivial manner have eluded you.

If you have a BTC address that existed since before CLAMS, go and try import your key in that wallet, or in LottoShares.

Quote

You are correct that the weakness of my system is that you need an online server but it could be feasible to build the system into the actual network.

Start a topic on that in development sub forum.