Quote from: joele on December 04, 2014, 01:47:17 PM
I think he will honor it by address, so it's better to save the private key.

Never delete private keys.
Ever.

Also, one backup is zero backups.

I think he will honor it by address, so it's better to save the private key.

Quote from: Frodo on December 04, 2014, 12:49:11 PM

Quote from: arubi on December 04, 2014, 12:09:27 PM

Quote from: sparkles on December 04, 2014, 04:32:20 AM
...
All blocks from the prior chain will be honored as well as the new chain.
...

Can't see my balance from the previous blockchain...

I think he didn't honor the blocks in the testnet genesis. It will just be honored in the final version.

Oh well, good enough.
Thanks.

Quote from: arubi on December 04, 2014, 12:09:27 PM

Quote from: sparkles on December 04, 2014, 04:32:20 AM
...
All blocks from the prior chain will be honored as well as the new chain.
...

Can't see my balance from the previous blockchain...

I think he didn't honor the blocks in the testnet genesis. It will just be honored in the final version.

Quote from: clayop on December 04, 2014, 10:32:09 AM
Mining is working fine on my dedicated server. But I am having an error message constantly

Code Select Expand

I am disconnecting peer x.x.x.x.:x for reason: You offered me a list of more sync blocks than could possibly exist


Same here - I think it  should work itself out when everyone updates

Quote from: sparkles on December 04, 2014, 04:32:20 AM
...
All blocks from the prior chain will be honored as well as the new chain.
...

Can't see my balance from the previous blockchain...

Quote from: clayop on December 04, 2014, 10:32:09 AM
Mining is working fine on my dedicated server. But I am having an error message constantly

Code Select Expand

I am disconnecting peer x.x.x.x.:x for reason: You offered me a list of more sync blocks than could possibly exist


Me too

Quote from: clayop on December 04, 2014, 10:59:31 AM
If there is a windows binary, it would be great.

+5% +5%

If there is a windows binary, it would be great.

Mining is working fine on my dedicated server. But I am having an error message constantly

I am disconnecting peer x.x.x.x.:x for reason: You offered me a list of more sync blocks than could possibly exist


Quote from: Troglodactyl on December 04, 2014, 07:24:44 AM

Quote from: smith7800 on December 04, 2014, 07:06:02 AM

Quote from: robrigo date=1417669260
Tried to compile the latest

n file included from /home/delegate/Sparkle/tests/dev_tests.cpp:3:0:
/home/delegate/Sparkle/tests/dev_fixture.hpp: In instantiation of 'void chain_fixture::produce_block(T) [with T = std::shared_ptr<bts::client::client>]':
/home/delegate/Sparkle/tests/dev_tests.cpp:55:25:   required from here
/home/delegate/Sparkle/tests/dev_fixture.hpp:231:59: error: 'struct bts::blockchain::full_block' has no member named 'nonce'
       while( b.difficulty() < SPK_MIN_DIFFICULTY ) b.nonce++;
                                                           ^
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2

Same here.  Anybody know a fix?

For now I'd ignore that. It's an error in the tests, not in the actual client.

Looks like just an orphaned test that didn't get removed or updated.

Thanks.  It's working, though the blocks seem to be coming mighty quickly (currently at 2251)

Quote from: smith7800 on December 04, 2014, 07:06:02 AM

Quote from: robrigo date=1417669260
Tried to compile the latest

n file included from /home/delegate/Sparkle/tests/dev_tests.cpp:3:0:
/home/delegate/Sparkle/tests/dev_fixture.hpp: In instantiation of 'void chain_fixture::produce_block(T) [with T = std::shared_ptr<bts::client::client>]':
/home/delegate/Sparkle/tests/dev_tests.cpp:55:25:   required from here
/home/delegate/Sparkle/tests/dev_fixture.hpp:231:59: error: 'struct bts::blockchain::full_block' has no member named 'nonce'
       while( b.difficulty() < SPK_MIN_DIFFICULTY ) b.nonce++;
                                                           ^
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2

Same here.  Anybody know a fix?

For now I'd ignore that. It's an error in the tests, not in the actual client.

Looks like just an orphaned test that didn't get removed or updated.

Quote from: smith7800 on December 04, 2014, 07:06:02 AM

Quote from: robrigo date=1417669260
Tried to compile the latest

n file included from /home/delegate/Sparkle/tests/dev_tests.cpp:3:0:
/home/delegate/Sparkle/tests/dev_fixture.hpp: In instantiation of 'void chain_fixture::produce_block(T) [with T = std::shared_ptr<bts::client::client>]':
/home/delegate/Sparkle/tests/dev_tests.cpp:55:25:   required from here
/home/delegate/Sparkle/tests/dev_fixture.hpp:231:59: error: 'struct bts::blockchain::full_block' has no member named 'nonce'
       while( b.difficulty() < SPK_MIN_DIFFICULTY ) b.nonce++;
                                                           ^
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2

Same here.  Anybody know a fix?

Same problem to one of my server.

Quote from: robrigo date=1417669260
Tried to compile the latest

n file included from /home/delegate/Sparkle/tests/dev_tests.cpp:3:0:
/home/delegate/Sparkle/tests/dev_fixture.hpp: In instantiation of 'void chain_fixture::produce_block(T) [with T = std::shared_ptr<bts::client::client>]':
/home/delegate/Sparkle/tests/dev_tests.cpp:55:25:   required from here
/home/delegate/Sparkle/tests/dev_fixture.hpp:231:59: error: 'struct bts::blockchain::full_block' has no member named 'nonce'
       while( b.difficulty() < SPK_MIN_DIFFICULTY ) b.nonce++;
                                                           ^
make[2]: *** [tests/CMakeFiles/dev_tests.dir/dev_tests.cpp.o] Error 1
make[1]: *** [tests/CMakeFiles/dev_tests.dir/all] Error 2
make: *** [all] Error 2

Same here.  Anybody know a fix?

Confirmed alpha.5 is working for me.

Quote from: Troglodactyl on December 04, 2014, 04:47:06 AM

Quote from: sparkles on December 04, 2014, 04:32:20 AM
I am starting a new test network with a new mining algorithm based on ECC signature. 

Your wallet must be unlocked to mine with the private key.  This is designed to maximize decentralization and eliminate mining pools.

All blocks from the prior chain will be honored as well as the new chain.

Difficulty adjusts every 20 blocks and is rate limited to +/- 2%

Excellent.  Will it still be at https://github.com/sparkle5/Sparkle?

This