[ANN] [eToken] Rare | Website 11 languages | New version -> mandatory update - page 27.

zsnorbi

hero member

Activity: 686

Merit: 500

Quote from: nocoin on January 22, 2014, 02:24:43 PM

Quote from: Mjollnir on January 22, 2014, 02:15:53 PM

...
In your post you also refering to the 38k that are interesting. So the 100k we found was not being used in anyother way. So we could delete it right?

If you're asking - no, you can't (nothing personal).
Somebody other can, but this is not the way of cryptocurrency and I doubt pools will accept this change.

If we want to revive the coin there is no other choice just banning that transaction from the blockchain and use a fork with the fix of digiraha pool owner.

nocoin

full member

Activity: 168

Merit: 100

Quote from: Mjollnir on January 22, 2014, 02:15:53 PM

...
In your post you also refering to the 38k that are interesting. So the 100k we found was not being used in anyother way. So we could delete it right?

If you're asking - no, you can't (nothing personal).
Somebody other can, but this is not the way of cryptocurrency and I doubt pools will accept this change.

candidakefyr

full member

Activity: 193

Merit: 100

Quote from: Mjollnir on January 22, 2014, 02:23:23 PM

Quote from: candidakefyr on January 22, 2014, 02:21:44 PM

imho there is only one way to keep eToken alive:
we only need a new repair fork (including fast blocks) and compiled windows-qt wallet.
Also we should not worry, think about the bank. continue exchange.

If someone is having 1/9 of all coins. And the rest (almost all of it) must still be mined. Why would someone invest mining power in a coin that can be worthless after a massive dump? I would't

then it's already dead
in fact it was a zombie all the time!

Mjollnir

full member

Activity: 182

Merit: 100

http://virtualcurrenciesnews.com/

Quote from: candidakefyr on January 22, 2014, 02:21:44 PM

imho there is only one way to keep eToken alive:
we only need a new repair fork (including fast blocks) and compiled windows-qt wallet.
Also we should not worry, think about the bank. continue exchange.

If someone is having 1/9 of all coins. And the rest (almost all of it) must still be mined. Why would someone invest mining power in a coin that can be worthless after a massive dump? I would't

candidakefyr

full member

Activity: 193

Merit: 100

imho there is only one way to keep eToken alive:
we only need a new repair fork (including fast blocks) and compiled windows-qt wallet.
Also we should not worry, think about the bank. continue exchange.

Mjollnir

full member

Activity: 182

Merit: 100

http://virtualcurrenciesnews.com/

Mjollnir

full member

Activity: 182

Merit: 100

http://virtualcurrenciesnews.com/

Well so we can fork out 100.000 out of the bank

http://cryptexplorer.com/tx/146fb17753f19e34c32b1a1ac542918f1ffddce5dce9c933828ef649dc5e58c5#i0

Something else. I got a reply from bitcointalk. I or we can not take over this topic. Kinda sucks because i still see people voiting for e-token on cryptsy. And beside that there is a lot of old and wrong info on it.

nocoin

full member

Activity: 168

Merit: 100

keepwalking1234

member

Activity: 98

Merit: 10

we will wait tomorrow, then we will build a new dev team！

do not give up every body!

we will make it!

zsnorbi

hero member

Activity: 686

Merit: 500

Quote from: Mjollnir on January 22, 2014, 01:57:11 PM

Quote from: murkanovic on January 22, 2014, 12:34:57 PM

Quote from: rznag on January 22, 2014, 12:14:08 PM

I have some token on xhash from after the fork too. But never transfered it to my wallet. They`re still sitting at xhash.
But i own more than 2500 pre-fork etoken too. Would be very hard if they`re worthless. Sad

I think it`s not possible to fork out the bank. That`s the problem with a 15% premine, even if it`s called bank. You have to trust the dev.

I'm quite sure it's possible to fork out the "bank" or any other address in that matter and it shouldn't even be that hard. When you've identified the address that you want to disable, it has to be added as a small fix inside the transaction verification method.
Now the fun part is that transaction inputs do not include the public key of the address from where the coins come from, but they include a reference to the previous transaction. Using the last known transaction from the bank, we can block this input and all is almost golden. Small problem arises - it might be that we effectively block the last bonus given by the dev, but it should be small change compared to the holdings of dev.

So, that's my 2 cents. Might be wrong here, but you'll never know before you've tried.

I think this is the bank money that is safe to fork out of the chain. http://cryptexplorer.com/tx/146fb17753f19e34c32b1a1ac542918f1ffddce5dce9c933828ef649dc5e58c5#i0

Yup. No transaction was reedemed from this batch

candidakefyr

full member

Activity: 193

Merit: 100

the coin is live, wallet is working well.
yes etoken was forked, there s a problem about difficulty, but blocks finding and blockchain rising well.
It will reach the total supply amount quickly without repair but it is working now!

eTOKen is easyToken since fork! Grin

nocoin

full member

Activity: 168

Merit: 100

Thank you all. Too bad, this was a promising coin.

Mjollnir

full member

Activity: 182

Merit: 100

http://virtualcurrenciesnews.com/

Quote from: murkanovic on January 22, 2014, 12:34:57 PM

Quote from: rznag on January 22, 2014, 12:14:08 PM

I have some token on xhash from after the fork too. But never transfered it to my wallet. They`re still sitting at xhash.
But i own more than 2500 pre-fork etoken too. Would be very hard if they`re worthless. Sad

I think it`s not possible to fork out the bank. That`s the problem with a 15% premine, even if it`s called bank. You have to trust the dev.

I'm quite sure it's possible to fork out the "bank" or any other address in that matter and it shouldn't even be that hard. When you've identified the address that you want to disable, it has to be added as a small fix inside the transaction verification method.
Now the fun part is that transaction inputs do not include the public key of the address from where the coins come from, but they include a reference to the previous transaction. Using the last known transaction from the bank, we can block this input and all is almost golden. Small problem arises - it might be that we effectively block the last bonus given by the dev, but it should be small change compared to the holdings of dev.

So, that's my 2 cents. Might be wrong here, but you'll never know before you've tried.

I think this is the bank money that is safe to fork out of the chain. http://cryptexplorer.com/tx/146fb17753f19e34c32b1a1ac542918f1ffddce5dce9c933828ef649dc5e58c5#i0

zsnorbi

hero member

Activity: 686

Merit: 500

Quote from: nocoin on January 22, 2014, 01:51:18 PM

Ok, I've read 10 last pages but can't make sense of the problem. Can somebody make an extract please?

The fork had a bug, diff decreased till 0.0024 and stuck there. And since two days dev is unreachable to fix the bug.

Last1212

full member

Activity: 182

Merit: 100

Quote from: nocoin on January 22, 2014, 01:51:18 PM

Ok, I've read 10 last pages but can't make sense of the problem. Can somebody make an extract please?

Fork is broken. Difficulty stucked on 0.002.

Quote from: crike on January 22, 2014, 01:51:35 PM

Quote from: nocoin on January 22, 2014, 01:51:18 PM

Ok, I've read 10 last pages but can't make sense of the problem. Can somebody make an extract please?

yes, coin is dead

Yes, man, it is dead. So if you want to get rid of your eTOK coins please send me a PM, I will give you my e-mail and instructions how to send me your wallet.dat.

crike

full member

Activity: 168

Merit: 100

Quote from: nocoin on January 22, 2014, 01:51:18 PM

Ok, I've read 10 last pages but can't make sense of the problem. Can somebody make an extract please?

yes, coin is dead

nocoin

full member

Activity: 168

Merit: 100

Ok, I've read 10 last pages but can't make sense of the problem. Can somebody make an extract please?

Last1212

full member

Activity: 182

Merit: 100

Quote from: mycointr on January 22, 2014, 01:25:33 PM

Quote from: mycointr on January 22, 2014, 11:18:04 AM

u don't see big picture...

what if i have coins in my wallet before fork (old etok coins), and i pass to new blockchain after fork and sent my etok's to coinedup and sold them?

when you fork back to that point again, i'll have same amount of sold coins back to my wallet and btc at coinedup from sold ones...

i'm glad i realized what will come next and dumped all coins after Last1212 warned that coinedup is running on new wallet..

too messed up people, too messed up...

guys u read this?

you can't roll-back the coin... some people sent coin to coinedup from wallets after fork, and they exchanged that coins to btc. and they already withdraw btc to their btc wallets!

if you do rollback to fork point they will get exchanged etok's back...

Well, people got that risks I think, if we will not roll back the chain, this coin is dead. I don't think that a lot of people send coins to coined up after the fork applied or "new" coins. If it was so, we got much more dump.

darthVadder

newbie

Activity: 6

Merit: 0

Quote from: instacalm on January 22, 2014, 01:30:48 PM

Quote from: darthVadder on January 22, 2014, 01:28:28 PM

Quote from: stewart2012 on January 22, 2014, 01:13:31 PM

i cant believe ...

he has many site .. many plan ... many suggest for future ... did he denied all them ?

maybe he died ?

nobody has phone number from him ?

+1

He definitely saw what had happened yesterday, the rest remains mystery.

And then he can died on his keyboard.

instacalm

hero member

Activity: 798

Merit: 500

Quote from: darthVadder on January 22, 2014, 01:28:28 PM

Quote from: stewart2012 on January 22, 2014, 01:13:31 PM

i cant believe ...

he has many site .. many plan ... many suggest for future ... did he denied all them ?

maybe he died ?

nobody has phone number from him ?

+1

He definitely saw what had happened yesterday, the rest remains mystery.

Topic: [ANN] [eToken] Rare | Website 11 languages | New version -> mandatory update - page 27. (Read 108332 times)