Notice:: PROJECT X, Come Join the Movement

[theprofileth]

I don't know if this has been said or not. Tired, long day and don't want to read every sentence.

1) Snapshot is taken.
2) Move your coins to another wallet.
3) Use private keys from original wallet that had your coins during the snapshot.

Problem solved. 

Yeah I already figured out that this was a decent solution however I am unclear whether or not every address is being implemented from all included coins because having to do something like that poses its own problems not to mention the inconvience of having to move coins that would otherwise receive PoS and now resetting your coin age

[URSAY]

I don't know if this has been said or not. Tired, long day and don't want to read every sentence.

1) Snapshot is taken.
2) Move your coins to another wallet.
3) Use private keys from original wallet that had your coins during the snapshot.

Problem solved. 

Yeah I already figured out that this was a decent solution however I am unclear whether or not every address is being implemented from all included coins because having to do something like that poses its own problems not to mention the inconvience of having to move coins that would otherwise receive PoS and now resetting your coin age

You wouldn't be moving coins by inputing your private key into his wallet.  You'd be showing him that you own the coins and you'd also be exposing those coins to security risks.  You could move your coins to a new wallet after the snapshot, yes.  But when the snapshot is taken would be decided by barwizi or his people while they potentially control your keys thru their software.  This leaves enough time for your keys to be exposed and your coins to be stolen.  If the pillage process is automated then it only takes a few seconds.

Problem NOT solved. 

[barwizi]

ah, i see

it will not work, can you guess why based off my post above or should i explain?

Well I have my notions but an explanation would be nice to understand things from your view
also yes I do understand how private keys work and no you haven't answered what i said before about being able to use dumprivkey after unlocking the wallet to get access to all the imported private keys for all addresses

Ok, simply, LBT uses on chain distribution, ie everyone is using the one single chain, so its just a script  that parses and get a sending address and sends coins back. If we were to send a signed message to a bitcoin node...how will we report your actual balance? From there where do we send the coins?

we could maybe start a new chain, people get the new chains addresses, but how then to allocate their share based on the % the held in each respective coin? using that method, we lose information such as balance, and price, which are key components in trying to distribute relative % with accuracy. Also there is no "static" point of reference from which to decide allocation so people can manipulate by using multiple addresses with negligible balances, or even no balance at all.  

[Hueristic]

Move coins to new key, send old key?

[barwizi]

I don't know if this has been said or not. Tired, long day and don't want to read every sentence.

1) Snapshot is taken.
2) Move your coins to another wallet.
3) Use private keys from original wallet that had your coins during the snapshot.

Problem solved. 

Yeah I already figured out that this was a decent solution however I am unclear whether or not every address is being implemented from all included coins because having to do something like that poses its own problems not to mention the inconvience of having to move coins that would otherwise receive PoS and now resetting your coin age

You wouldn't be moving coins by inputing your private key into his wallet.  You'd be showing him that you own the coins and you'd also be exposing those coins to security risks.  You could move your coins to a new wallet after the snapshot, yes.  But when the snapshot is taken would be decided by barwizi or his people while they potentially control your keys thru their software.  This leaves enough time for your keys to be exposed and your coins to be stolen.  If the pillage process is automated then it only takes a few seconds.

Problem NOT solved. 

All in all the problem is on the user side, not the developer side. Your concerns while valid still fall under the category of user security.

In this case what we are attempting to do is like Microsoft trying  to create a Login policy that takes into account that yo have a 5 year old at home and a teenager who sometimes leaves the wi-fi on in public.

All i can do is map the balances on the chain and tel people how to redeem. The concerns about the code are invalid since it is open source and can be reviewed at launch. Since there is no mining rush, people can take their time to redeem their share after getting a report on the code. As for Binaries, i would suggest using those compiled by me and me alone, no third party code.

Snapshot dates are not arbitrary, they are announced and adhered to, look at NoirShares, Lottoshares, MMC BTSX and many others have all used this method successfully without incident. And on another note, actually he is right in his own way!! Problem indeed solved. if you do not trust me or the people who review the code also not trusting yourself to view the code, you can simply redeem offline, send to a new wallet and destroy the one you used to redeem.

[barwizi]

Move coins to new key, send old key?

With my method, there are no keys exchanged at all. So apart from getting free coins, you also get anonymity as a bonus.

[barwizi]

Sync added

[smith coins]

looking forward to this Project
good luck

[theprofileth]

Move coins to new key, send old key?

With my method, there are no keys exchanged at all. So apart from getting free coins, you also get anonymity as a bonus.

He is saying that you would move your coins to a new key, wait for the snapshot then move your coins back to your primary key and use the snapshotted key to prevent you/others from getting your primary key
I think more explanation is needed for example when you claim your coins do you have them under the same address but in the project x chain?

[barwizi]

Move coins to new key, send old key?

With my method, there are no keys exchanged at all. So apart from getting free coins, you also get anonymity as a bonus.

He is saying that you would move your coins to a new key, wait for the snapshot then move your coins back to your primary key and use the snapshotted key to prevent you/others from getting your primary key
I think more explanation is needed for example when you claim your coins do you have them under the same address but in the project x chain?

If you happened to be holding NRS before our snapshot you could have a live demonstration, no, the address changes to fit the prefix of the new chain,, it does not remain the same.

[theprofileth]

Move coins to new key, send old key?

With my method, there are no keys exchanged at all. So apart from getting free coins, you also get anonymity as a bonus.

He is saying that you would move your coins to a new key, wait for the snapshot then move your coins back to your primary key and use the snapshotted key to prevent you/others from getting your primary key
I think more explanation is needed for example when you claim your coins do you have them under the same address but in the project x chain?

If you happened to be holding NRS before our snapshot you could have a live demonstration, no, the address changes to fit the prefix of the new chain,, it does not remain the same.

Ok now this is actually a technical question, how does 1 private key produce multiple public keys? Or does it? I am confused because I don't quiet understand how if we import a private key into your blockchain how will the blockchain be able to know the private key for another chain's public key? I mean I did participate in converting my noirstake to noirstake 2.0 but I just imagined that was because of the same code base.

[barwizi]

Move coins to new key, send old key?

With my method, there are no keys exchanged at all. So apart from getting free coins, you also get anonymity as a bonus.

He is saying that you would move your coins to a new key, wait for the snapshot then move your coins back to your primary key and use the snapshotted key to prevent you/others from getting your primary key
I think more explanation is needed for example when you claim your coins do you have them under the same address but in the project x chain?

If you happened to be holding NRS before our snapshot you could have a live demonstration, no, the address changes to fit the prefix of the new chain,, it does not remain the same.

Ok now this is actually a technical question, how does 1 private key produce multiple public keys? Or does it? I am confused because I don't quiet understand how if we import a private key into your blockchain how will the blockchain be able to know the private key for another chain's public key?

the keys are unique to each other, you'll need to understand bitcoin base58 for total understanding , but basically each matching pair can be converted to another version , for example, Bitcoin uses 1 as it's prefix so if we want that key to fit for example NoirShares, we need to convert to 0x35 == 53 which is N .

its the same key, just converted to match our prefix

[vipgelsi]

Wanst this a movie in the 80's? 

[chocobo]

Beware of this dev, he has taken tons of BTC from Noir Group including most of an ICO and a 10% premine. This thread explains further:

https://bitcointalk.org/index.php?topic=791890.new#new

Notice that the premine of XUC will be much larger than 1% because likely less that 5% of snapshot coins will be claimed

[darylluke]

I know it is a young coin, but I submit LTCD for this project, too. I hope you guys like it enough to include it in your new project here!! thnx.

https://bitcointalk.org/index.php?topic=760143.0

~darylluke.

[sidhujag]

plz add devcoin to the list

[Mr Harrison]

Every big exchange will love this coin. Massive shares. Am i right?

[noerc]

I don't really understand the idea of this project. So the devs of all participating coins should hardfork to your 1% premine PoW coin and half of the coin supply will be distributed over the non-zero balance addresses weighted by normalized market cap? I mean the old blockchains still exist, do you want the devs to abandon their projects to join this one? Then someone else could pick up the development on the old chain and keep the market cap in the original coin.

BTW, most of the developers of the coins in the list would be able to arrange the same thing without you and without the 1% premine.

[barwizi]

I don't really understand the idea of this project. So the devs of all participating coins should hardfork to your 1% premine PoW coin and half of the coin supply will be distributed over the non-zero balance addresses weighted by normalized market cap? I mean the old blockchains still exist, do you want the devs to abandon their projects to join this one? Then someone else could pick up the development on the old chain and keep the market cap in the original coin.

BTW, most of the developers of the coins in the list would be able to arrange the same thing without you and without the 1% premine.

Noone is hardforking anything, and people can continue on their chains, they are simply being given a share in this with no strings attached. No dev is asked to join this project or abandon his , please take time to read the OP properly as everything is there.

BTW, most of the developers of the coins in the list would be able to arrange the same thing without you and without the 1% premine.

But they did not come up with the idea did they? Anyone can fork the chain or copy my idea if they wish , such is crypto. But in the end, if all you can do is copy someone else's ideas, you don't amount to much do you?

[picchio]

...
How to get your Coins
--------------------------

...
type dumpprivkey "insertyouraddresshere" and copy the result.

Then in the XUC wallet

HELP--> DEBUG WINDOW --> CONSOLE

type importprivkey "yourprivatekeyhere",

Why do not use signmessage?
signmessage <CoinAddress> <message>
Sign a message with the private key of an address