[ANN][XEL] Elastic Project - The Decentralized Supercomputer

[HmmMAA]

Someone can help me with clarification of the price of ICO?

Average price per XEL ( as XEL per BTC was decreasing over ICO time ) is close to 700 satoshis .

[Bgjjj2016]

About someone pulling the strings;

Ive been the community manager of QORA and in very hard times I kept the spirit alive in the community. Beside that I found new devs together with Vrontis(another community member) for the project, Because the Qora founder/dev gave the project to the community.

I also set up the twitter campaign, which resulted in almost 3k followers as we speak.

I did frequent updates and did my very best to help with the marketing and brought the right people together.

Vrontis and me left the project after we managed it to give it in good hands. Today Qora is more alive then ever, with very good devs and the community manager of Burst leading the project.

I'm more then happy to do this also for The Elastic Project. I do have an very busy schedule in daily life, so this would be an part time job. This was also the case for the Qora project.

For my work in QORA I received a significant amount of Qora initially from the founder.

So also in this case, I think its very important to create an foundation where people who will actively help the project will get an compensation. If it's me ore someone else, its more then fair that to receive something for the efforts that people make. There are also people who have more then enough and can afford to help just from their love for an project, which of course also would be great.

So just to summarise what I can offer:

-Keep the spirit alive
-Set up a twitter campaign
-Approach marketing company's and get the word out there
-Find the right people who will create promo videos and a website( I know a good one in the crypto community for a good price)
-Just all the non technical manageable stuff

Let me know!

Keep the spirits alive ? Are you kidding us ? We have great sprits here. Our wonderful Devs have worked free all these months. If we have to pay anyone, it should be the hard working devs here. Don't worry about our spirits   

[Selerius]

EK, Sorry for taking your time. When I go to Electrum and put my private key, I get this message "
No inputs found ( Note that inputs need to be confirmed)". Could you please help ? Thank you !

For both you and any others encountering it, here might be a solution for the Electrum "no inputs found" error, hopefully anyway:

https://bitcointalk.org/index.php?topic=1480406.msg14925130#msg14925130

[techwriterjoe]

I made payment to the ICO with a Bitgo wallet: https://www.bitgo.com/p2sh_safe_address

It is a p2sh multi-signature wallet. Meaning, the BTC address starts with a 3.

After I made payment, on the Elastic bitcointalk threads, EK and others assured me, more than once, that this type of wallet is fine. They stated that all I would need is my private key, which I still have.

The stated solution for this type of wallet was to deposit some small amount of coin into the account and then I would be able to enter those transaction details into the Elastic wallet to verify that I was the true owner of the BTC address wallet and XEL.

Has this been implemented? Is it in the roadmap?

I currently have no way to figure out how much XEL I have. Although, I can identify my transactions on the original genesis block.

I am very impressed with this project but I have brought these issues up before without any feedback. They are valid questions.

Thanks in advance. -Joe

[techwriterjoe]

Some earlier discussion of the Multi Sig wallets was on page 24 of this thread:

https://bitcointalk.org/index.php?topic=1396233.msg14526149#msg14526149

[Evil-Knievel]

Some earlier discussion of the Multi Sig wallets was on page 24 of this thread:

https://bitcointalk.org/index.php?topic=1396233.msg14526149#msg14526149

So you have a 2-of-3 multisig wallet and you have 2-of-3 private keys (so main key and backup key)? If yes, then it's already implemented. If not, we could think about another alternative way to redeem - broadcast a handcrafted transaction and use this TX signature for verification. But the latter one would have to be decided by the entire community I guess.  

Technically, someone who can sign a transaction from a multisig wallet has access to this wallet, so from my point of you this remeed scheme might be valid. Not sure about how this scheme could be used to steal commonly owned XEL, since a signed TX is different from a signed message in terms of transparency.

[techwriterjoe]

Some earlier discussion of the Multi Sig wallets was on page 24 of this thread:

https://bitcointalk.org/index.php?topic=1396233.msg14526149#msg14526149

So you have a 2-of-3 multisig wallet and you have 2-of-3 private keys (so main key and backup key)? If yes, then it's already implemented. If not, we could think about another alternative way to redeem - broadcast a handcrafted transaction and use this TX signature for verification. But the latter one would have to be decided by the entire community I guess. 

Technically, someone who can sign a transaction from a multisig wallet has access to this wallet, so from my point of you this remeed scheme might be valid. Not sure about how this scheme could be used to steal commonly owned XEL, since a signed TX is different from a signed message in terms of transparency.

Yes, I have both keys. If it's already implemented, then that's a huge relief.

I've been rooting for you guys for about a year and was never quite sure if I was actually going to be able to redeem my share. It's really cool to see this project keep going.

Now, I just need to figure out how many XEL I have. I know the tranx #s. Anybody know how this could be done?

Thanks again.

[Thefrolly]

Some earlier discussion of the Multi Sig wallets was on page 24 of this thread:

https://bitcointalk.org/index.php?topic=1396233.msg14526149#msg14526149

So you have a 2-of-3 multisig wallet and you have 2-of-3 private keys (so main key and backup key)? If yes, then it's already implemented. If not, we could think about another alternative way to redeem - broadcast a handcrafted transaction and use this TX signature for verification. But the latter one would have to be decided by the entire community I guess. 

Technically, someone who can sign a transaction from a multisig wallet has access to this wallet, so from my point of you this remeed scheme might be valid. Not sure about how this scheme could be used to steal commonly owned XEL, since a signed TX is different from a signed message in terms of transparency.

Yes, I have both keys. If it's already implemented, then that's a huge relief.

I've been rooting for you guys for about a year and was never quite sure if I was actually going to be able to redeem my share. It's really cool to see this project keep going.

Now, I just need to figure out how many XEL I have. I know the tranx #s. Anybody know how this could be done?

Thanks again.

https://dl.dropboxusercontent.com/u/21000833/Elastic/Icolist/Ico-list.txt

[Evil-Knievel]

Some earlier discussion of the Multi Sig wallets was on page 24 of this thread:

https://bitcointalk.org/index.php?topic=1396233.msg14526149#msg14526149

So you have a 2-of-3 multisig wallet and you have 2-of-3 private keys (so main key and backup key)? If yes, then it's already implemented. If not, we could think about another alternative way to redeem - broadcast a handcrafted transaction and use this TX signature for verification. But the latter one would have to be decided by the entire community I guess.  

Technically, someone who can sign a transaction from a multisig wallet has access to this wallet, so from my point of you this remeed scheme might be valid. Not sure about how this scheme could be used to steal commonly owned XEL, since a signed TX is different from a signed message in terms of transparency.

Yes, I have both keys. If it's already implemented, then that's a huge relief.

Go to http://ec2-52-57-31-137.eu-central-1.compute.amazonaws.com:6876/index.html
Click the "Humanoid" Icon left to the text box, log in with some crap passphrase.
Then, in the upper left corner click Redeem and find your address along with the balance in the "unclaimed XEL" list.

Your address means one of the addresses inside your multisig. This is shitty at the moment, I think we should list the multisig address here as well. Just convert one of your keys to a BTC address and look it up there.

EDIT: Duuuuude, just see that someone owns over 5 million XEL in one address  . I have never noticed that before.

[techwriterjoe]

Some earlier discussion of the Multi Sig wallets was on page 24 of this thread:

https://bitcointalk.org/index.php?topic=1396233.msg14526149#msg14526149

So you have a 2-of-3 multisig wallet and you have 2-of-3 private keys (so main key and backup key)? If yes, then it's already implemented. If not, we could think about another alternative way to redeem - broadcast a handcrafted transaction and use this TX signature for verification. But the latter one would have to be decided by the entire community I guess. 

Technically, someone who can sign a transaction from a multisig wallet has access to this wallet, so from my point of you this remeed scheme might be valid. Not sure about how this scheme could be used to steal commonly owned XEL, since a signed TX is different from a signed message in terms of transparency.

Yes, I have both keys. If it's already implemented, then that's a huge relief.

I've been rooting for you guys for about a year and was never quite sure if I was actually going to be able to redeem my share. It's really cool to see this project keep going.

Now, I just need to figure out how many XEL I have. I know the tranx #s. Anybody know how this could be done?

Thanks again.

https://dl.dropboxusercontent.com/u/21000833/Elastic/Icolist/Ico-list.txt

I've been through this.

There is no way to identify my transactions. My BTC address is multi signature. It starts with a 3.

I think these somehow get converted to the longer addresses that are listed on that link such as:
2-1HPRacvTUSPXzFB1xuYkAftZ9R9kiLz3y9-1PxGBYYjjc5aKVe38s9JEwqHPinGVntyn2-1Mh1bm4MJA9LFreL5fLynKR4GEaEns4xGU

But I'm not even sure of that.

Basically, if you have a multi sig address, there is no way to identify the XEL line items on the link you shared.

Any help?

[Evil-Knievel]

Some earlier discussion of the Multi Sig wallets was on page 24 of this thread:

https://bitcointalk.org/index.php?topic=1396233.msg14526149#msg14526149

So you have a 2-of-3 multisig wallet and you have 2-of-3 private keys (so main key and backup key)? If yes, then it's already implemented. If not, we could think about another alternative way to redeem - broadcast a handcrafted transaction and use this TX signature for verification. But the latter one would have to be decided by the entire community I guess.  

Technically, someone who can sign a transaction from a multisig wallet has access to this wallet, so from my point of you this remeed scheme might be valid. Not sure about how this scheme could be used to steal commonly owned XEL, since a signed TX is different from a signed message in terms of transparency.

Yes, I have both keys. If it's already implemented, then that's a huge relief.

I've been rooting for you guys for about a year and was never quite sure if I was actually going to be able to redeem my share. It's really cool to see this project keep going.

Now, I just need to figure out how many XEL I have. I know the tranx #s. Anybody know how this could be done?

Thanks again.

https://dl.dropboxusercontent.com/u/21000833/Elastic/Icolist/Ico-list.txt

I've been through this.

There is no way to identify my transactions. My BTC address is multi signature. It starts with a 3.

I think these somehow get converted to the longer addresses that are listed on that link such as:
2-1HPRacvTUSPXzFB1xuYkAftZ9R9kiLz3y9-1PxGBYYjjc5aKVe38s9JEwqHPinGVntyn2-1Mh1bm4MJA9LFreL5fLynKR4GEaEns4xGU

But I'm not even sure of that.

Basically, if you have a multi sig address, there is no way to identify the XEL line items on the link you shared.

Any help?

I will fix this annoying thing today.
For now, just do this:

1. Find your multisig wallet in blockchain.info (Example: https://blockchain.info/address/3QJmV3qfvL9SuYo34YihAf3sRCW3qSinyC)
2. Click on an outgoing transaction (Example: https://blockchain.info/tx/2962c5be49f39b8f86dba0e7e6f67276103a8606f4b5af8b22fe161c76e4922d)
3. Click "Show Scripts & Coinbase" to see more details.
You will find a long line like this. You want that part (last block of blocks separated by a space) which is BOLD here:

OP_FALSE 30450221008cc26382b0a617b20ef4e2f451e2b23fdf0a47ee10ef4cbcb84ab9bbdda3b1b402203 f953c024cae8e5302d61d869ed28c8ab129e1192b5abe8d7e5a586bddeabd8401 3044022001bb3587913e90e786a69e8aa02cb4a1aa75af8e1d2b5f0a2cf641ef936f129c022012f 4c0549ccaa5ea585452e0cdb4250a94a7bddbc4312e1e2b6da8f33828337501 52410491bba2510912a5bd37da1fb5b1673010e43d2c6d812c514e91bfa9f2eb129e1c183329db5 5bd868e209aac2fbc02cb33d98fe74bf23f0c235d6126b1d8334f864104865c40293a680cb9c020 e7b1e106d8c1916d3cef99aa431a56d253e69256dac09ef122b1a986818a7cb624532f062c1d1f8 722084861c5c3291ccffef4ec687441048d2455d2403e08708fc1f556002f1b6cd83f992d085097 f9974ab08a28838f07896fbab08f39495e15fa6fad6edbfb1e754e35fa1c7844c41f322a1863d46 21353ae   

4. Paste it here
https://chainquery.com/bitcoin-api/decodescript
and click "Execute Command"

5. Find your 3 addresses in the output. Example:

Code:

{
	"result": {
		"asm": "2 0491bba2510912a5bd37da1fb5b1673010e43d2c6d812c514e91bfa9f2eb129e1c183329db55bd868e209aac2fbc02cb33d98fe74bf23f0c235d6126b1d8334f86 04865c40293a680cb9c020e7b1e106d8c1916d3cef99aa431a56d253e69256dac09ef122b1a986818a7cb624532f062c1d1f8722084861c5c3291ccffef4ec6874 048d2455d2403e08708fc1f556002f1b6cd83f992d085097f9974ab08a28838f07896fbab08f39495e15fa6fad6edbfb1e754e35fa1c7844c41f322a1863d46213 3 OP_CHECKMULTISIG",
		"reqSigs": 2,
		"type": "multisig",
		"addresses": [
			"139FpKh63Vn4Y73ijtyqq8A6XESH8brxqs",
			"1PNvbXZFysxvx3252w9JHMa7zbG95snqnm",
			"1jqo3ptYSnUhCJq75MMyRuwC2zNyQqRy3"
		],
		"p2sh": "3QJmV3qfvL9SuYo34YihAf3sRCW3qSinyC"
	},
	"error": null,
	"id": null
}

6. Look up one of them in the redeem list.

[Evil-Knievel]

Did it work?

[techwriterjoe]

Did it work?

Yessssssss. I finally know how many XEL I have. Awesome. Thanks man. The upcoming months are going to be crazy.

[techwriterjoe]

So has anyone been on a testnet, for example http://ec2-52-57-31-137.eu-central-1.compute.amazonaws.com:6876/index.html, and actually able to test redeem?

[Evil-Knievel]

So has anyone been on a testnet, for example http://ec2-52-57-31-137.eu-central-1.compute.amazonaws.com:6876/index.html, and actually able to test redeem?

Many have done it already. The testnet will be reset soon, however.

[techwriterjoe]

So has anyone been on a testnet, for example http://ec2-52-57-31-137.eu-central-1.compute.amazonaws.com:6876/index.html, and actually able to test redeem?

Many have done it already. The testnet will be reset soon, however.

OK, yea, I figured. I'm behind here obviously. I put in my info. It kept saying invalid signatures. I'll assume the testnet just needs to be reset.

Thanks again EK.

[devking]

So has anyone been on a testnet, for example http://ec2-52-57-31-137.eu-central-1.compute.amazonaws.com:6876/index.html, and actually able to test redeem?

Many have done it already. The testnet will be reset soon, however.

EK, I'm not able to redeem XEL on testnet, I'm using electrum wallet to sign message. getting following error

Could not validate unsigned bytes returned by the server.

[Evil-Knievel]

So has anyone been on a testnet, for example http://ec2-52-57-31-137.eu-central-1.compute.amazonaws.com:6876/index.html, and actually able to test redeem?

Many have done it already. The testnet will be reset soon, however.

EK, I'm not able to redeem XEL on testnet, I'm using electrum wallet to sign message. getting following error

Could not validate unsigned bytes returned by the server.

Yeah this public XEL node sucks. If you run it all locally, it works fine. I have put this bug on the todo list ;-)

[BTCspace]

just come back to show some community spirit.

[wizzardTim]

Is it safe to test the redeem function with this server (http://ec2-52-57-31-137.eu-central-1.compute.amazonaws.com:6876)? Or someone can steal the recovery phrase from the btc wallet?