[ANN] [eToken]Important announcement eToken

[rznag]

wallet link isnt working for me... it keeps hanging on that MEGA loading circle

tried chrome and internet explorer and firefox...

May i suggest a google link 2?  

uploaded it to my dropbox too..
https[Suspicious link removed]

I will use your link oke?

sure...or we upload it somewhere else...

[1715255479]

1715255479

[1715255479]

1715255479

[1715255479]

1715255479

[Randy pNut]

wallet link isnt working for me... it keeps hanging on that MEGA loading circle

tried chrome and internet explorer and firefox...

May i suggest a google link 2?  

uploaded it to my dropbox too..
https[Suspicious link removed]

I will use your link oke?

sure...or we upload it somewhere else...

http://downftp.e-token.org/etoken-qt.zip

[Anacronix]

Love to see that diff is working and etoken is still hard to mine 

[Mjollnir]

wallet link isnt working for me... it keeps hanging on that MEGA loading circle

tried chrome and internet explorer and firefox...

May i suggest a google link 2?  

uploaded it to my dropbox too..
https[Suspicious link removed]

I will use your link oke?

sure...or we upload it somewhere else...

http://downftp.e-token.org/etoken-qt.zip

You have access to the FTP of that subdomain. Also to the rest?

Edit i just see you have

[suncoastbuddy]

e-token.org is retaken

now redirect on e-token.info

dev back and supporting coin?

i don't think he'll, just retook some accounts.

He did mention it 

[Mjollnir]

e-token.org is retaken

now redirect on e-token.info

dev back and supporting coin?

i don't think he'll, just retook some accounts.

He did mention it  

You are right I just read it wrong.   Thats why i got a extra twitter acount lol. Well does't matter :-) @etokencoin is a good one

Great  

[illodin]

Is this retake, dev account will support and retook!
Problem was but retook dev is new!    This so much and will go beyond!

[thisisnotmyltcusername]

if you wanna lobby properly, at least post this Etoken Retaken thread url with your coinmarket.io requests, as stated in coinmarket suggestion thread

[simplemind]

I have two questions.

1) How do you prevent transactions from/to old "bank"?
2) Is anyone besides digiraha finding blocks?

[affan]

well done 

[thisisnotmyltcusername]

I have two questions.

1) How do you prevent transactions from/to old "bank"?
2) Is anyone besides digiraha finding blocks?

1 - 100k block blacklist is in the new source
https://github.com/digiraha/etoken/blob/master/src/blockedinputs.cpp

2 - No since 99% of miners are there for now. Expect some to migrate if digiraha gets a downtime but not especially before  

[simplemind]

I have two questions.

1) How do you prevent transactions from/to old "bank"?
2) Is anyone besides digiraha finding blocks?

1 - blacklisted adresses are hardcoded in the new source
2 - No since 99% of miners are there for now. Expect some to migrate if digiraha gets a downtime but not especially before  

1) That's what I was afraid. It's done by 'isBankInput' function, right? You just run this on every transaction. You might probably know that this is a HUGE performance issue. I was wondering why the new client reqiures so much compute power...

2) I did some solo mining on my linux box and found a block but that just crashed the client:
2014-01-29 12:54:45,198 INFO template_registry # Yay, share with diff above 100000
2014-01-29 12:54:45,199 INFO template_registry # We found a block candidate! 00000000355cee72d59b041e843acaf27                           22d0e072a4090f96eca5bf0f7843328
2014-01-29 12:54:46,200 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:51,201 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:56,205 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
.
.
.

When compiling the client I get a couple of warnings. The original client had no warnings. Example:
db/db_impl.cc: In member function âvirtual bool leveldb::DBImpl::GetProperty(const leveldb::Slice&, std::string*)â:
db/db_impl.cc:1347:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]


I then tried to run the test suite on the code. Result:
*** 402 failures detected in test suite "eToken Test Suite"

So I suspect the client might not be 100% stable...

[Mjollnir]

I have two questions.

1) How do you prevent transactions from/to old "bank"?
2) Is anyone besides digiraha finding blocks?

1 - blacklisted adresses are hardcoded in the new source
2 - No since 99% of miners are there for now. Expect some to migrate if digiraha gets a downtime but not especially before  

1) That's what I was afraid. It's done by 'isBankInput' function, right? You just run this on every transaction. You might probably know that this is a HUGE performance issue. I was wondering why the new client reqiures so much compute power...

2) I did some solo mining on my linux box and found a block but that just crashed the client:
2014-01-29 12:54:45,198 INFO template_registry # Yay, share with diff above 100000
2014-01-29 12:54:45,199 INFO template_registry # We found a block candidate! 00000000355cee72d59b041e843acaf27                           22d0e072a4090f96eca5bf0f7843328
2014-01-29 12:54:46,200 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:51,201 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:56,205 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
.
.
.

When compiling the client I get a couple of warnings. The original client had no warnings. Example:
db/db_impl.cc: In member function âvirtual bool leveldb::DBImpl::GetProperty(const leveldb::Slice&, std::string*)â:
db/db_impl.cc:1347:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]


I then tried to run the test suite on the code. Result:
*** 402 failures detected in test suite "eToken Test Suite"

So I suspect the client might not be 100% stable...

On point 1. When its just being running i got arround the same resources as the preminecoin (yeh lol). Did not really notice it when making a transacion. Can keep a eye on that.

On point 2. Better ask murkanovic 

[Mjollnir]

We do need to get some other pools finding blocks. Just put my miner to http://etok.smartmining.net/

[simplemind]

I have two questions.

1) How do you prevent transactions from/to old "bank"?
2) Is anyone besides digiraha finding blocks?

1 - blacklisted adresses are hardcoded in the new source
2 - No since 99% of miners are there for now. Expect some to migrate if digiraha gets a downtime but not especially before  

1) That's what I was afraid. It's done by 'isBankInput' function, right? You just run this on every transaction. You might probably know that this is a HUGE performance issue. I was wondering why the new client reqiures so much compute power...

2) I did some solo mining on my linux box and found a block but that just crashed the client:
2014-01-29 12:54:45,198 INFO template_registry # Yay, share with diff above 100000
2014-01-29 12:54:45,199 INFO template_registry # We found a block candidate! 00000000355cee72d59b041e843acaf27                           22d0e072a4090f96eca5bf0f7843328
2014-01-29 12:54:46,200 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:51,201 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:56,205 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
.
.
.

When compiling the client I get a couple of warnings. The original client had no warnings. Example:
db/db_impl.cc: In member function âvirtual bool leveldb::DBImpl::GetProperty(const leveldb::Slice&, std::string*)â:
db/db_impl.cc:1347:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]


I then tried to run the test suite on the code. Result:
*** 402 failures detected in test suite "eToken Test Suite"

So I suspect the client might not be 100% stable...

On point 1. When its just being running i got arround the same resources as the preminecoin (yeh lol). Did not really notice it when making a transacion. Can keep a eye on that.

On point 2. Better ask murkanovic 

1) I don't mind, and I'm not mining anymore. Was just curious. Maybe my findings can help improve the coin, since I still like it.

2) murkanovic, did you run the test suite?

[thisisnotmyltcusername]

there's zero noticeable difference indeed in running that unless you use a CPU from previous century at least  
the deamon will still take you between 0.00 and 0.01% CPU ressources on common intel dual/quadcores (i3/I5), so yeah you have a damn insane margin before it becomes a problem even with the slowest celeron...

so much "compute power"... Even my lightweight midori browser must use 50x more... 

edit : and zero problem/warning to compile on ubuntu either

[rznag]

I have two questions.

1) How do you prevent transactions from/to old "bank"?
2) Is anyone besides digiraha finding blocks?

1 - blacklisted adresses are hardcoded in the new source
2 - No since 99% of miners are there for now. Expect some to migrate if digiraha gets a downtime but not especially before  

1) That's what I was afraid. It's done by 'isBankInput' function, right? You just run this on every transaction. You might probably know that this is a HUGE performance issue. I was wondering why the new client reqiures so much compute power...

2) I did some solo mining on my linux box and found a block but that just crashed the client:
2014-01-29 12:54:45,198 INFO template_registry # Yay, share with diff above 100000
2014-01-29 12:54:45,199 INFO template_registry # We found a block candidate! 00000000355cee72d59b041e843acaf27                           22d0e072a4090f96eca5bf0f7843328
2014-01-29 12:54:46,200 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:51,201 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
2014-01-29 12:54:56,205 ERROR bitcoin_rpc_manager # Problem with Pool 0 -- NO ALTERNATE POOLS!!!
.
.
.

When compiling the client I get a couple of warnings. The original client had no warnings. Example:
db/db_impl.cc: In member function âvirtual bool leveldb::DBImpl::GetProperty(const leveldb::Slice&, std::string*)â:
db/db_impl.cc:1347:33: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]


I then tried to run the test suite on the code. Result:
*** 402 failures detected in test suite "eToken Test Suite"

So I suspect the client might not be 100% stable...

On point 1. When its just being running i got arround the same resources as the preminecoin (yeh lol). Did not really notice it when making a transacion. Can keep a eye on that.

On point 2. Better ask murkanovic 

It compiled without errors or warnings for me on linux.
And in db_impl.cc was nothing changed. Last change there was from original dev 22 days ago. See here:
https://github.com/digiraha/etoken/tree/master/src/leveldb/db

[Mjollnir]

Changed some info on the main page


Latest news: e-token.org will host services around eTOK and altcoins. e-token.info is the official info site for eToken.


how about that 

[Anacronix]

so lemme think. The first dev waited for the fix and now is back ? He let others fix it , while keeping some of his premine ? Hmm...

[Anacronix]

doesn't say anything about how they got hold of e-token.org.