Anyone confirm?
getblockhash 378
fa75173cc87cd6d80b104fe990a09d8aa039328da9119bf6b968fff7e41be47d
getblockhash 378
fa75173cc87cd6d80b104fe990a09d8aa039328da9119bf6b968fff7e41be47d
Confirm
confirm
Topic: Re: [AXIOM] AxiomMemHash, Schnorr Sigs Implemented, APOS 3.0, AXH 2.0 Proposed - page 148. (Read 204903 times)
July 26, 2015, 12:39:29 AM
Confirm
confirm
July 26, 2015, 12:38:57 AM
Anyone confirm?
getblockhash 378
fa75173cc87cd6d80b104fe990a09d8aa039328da9119bf6b968fff7e41be47d
getblockhash 378
fa75173cc87cd6d80b104fe990a09d8aa039328da9119bf6b968fff7e41be47d
Confirm
July 26, 2015, 12:37:54 AM
Anyone confirm?
getblockhash 378
fa75173cc87cd6d80b104fe990a09d8aa039328da9119bf6b968fff7e41be47d
getblockhash 378
fa75173cc87cd6d80b104fe990a09d8aa039328da9119bf6b968fff7e41be47d
July 26, 2015, 12:37:32 AM
A lot of forks are happening. 
Diff is rising and we are adding two more strong nodes now.
The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
Diff is rising and we are adding two more strong nodes now.The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
i still fork with this nodes
OFFICIAL CHECKPOINTING NODES are on block 341. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!!
A 32bit wallet dev ?
The algo is very inefficient in 32 bit mode but we have included the code to compile in axiom-qt.pro if you like:
DEFINES += USE_NUM_NONE USE_FIELD_INV_BUILTIN USE_SCALAR_INV_BUILTIN
# 64-bit
#DEFINES += USE_FIELD_5X52 USE_SCALAR_4X64
# 32-bit
DEFINES += USE_FIELD_10X26 USE_SCALAR_8X32
July 26, 2015, 12:35:11 AM
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now.
The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
Diff is rising and we are adding two more strong nodes now.The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
i still fork with this nodes
OFFICIAL CHECKPOINTING NODES are on block 341. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!!
A 32bit wallet dev ?
The algo is very inefficient in 32 bit mode but we have included the code to compile in axiom-qt.pro if you like:
DEFINES += USE_NUM_NONE USE_FIELD_INV_BUILTIN USE_SCALAR_INV_BUILTIN
# 64-bit
#DEFINES += USE_FIELD_5X52 USE_SCALAR_4X64
# 32-bit
DEFINES += USE_FIELD_10X26 USE_SCALAR_8X32
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now.
NEW ADDNODES
The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
addnode=162.222.181.215
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
Diff is rising and we are adding two more strong nodes now.NEW ADDNODES
The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
addnode=162.222.181.215
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
i still fork with this nodes
OFFICIAL CHECKPOINTING NODES are on block 379. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!!
PRESS WINDOWS + R, ENTER:
notepad %APPDATA%/axiom/axiom.conf
ADD THIS TO THE FILE:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We're adding two more nodes now. Syncing is taking forever. If you have a node running with server=1 daemon=1 and youre around block 380, share your IP for addnode!
July 26, 2015, 12:34:14 AM
I successfully synced myself to the correct chain. I suggest deleting everything in ~/.axiom on linux, and clearing your Axiom folder in your AppData folder on Windows (except the wallet.dat).
Clearing those files allowed me to sync properly. Best of luck!
Clearing those files allowed me to sync properly. Best of luck!
na it is still forked lads who neveer closed their wallets are running their own chains. that is the reason deleting block data wont fix this issue. im afraid at present only relaunch will be the fix with proper nodes.
Well If there is a relaunch , maybe dev will put up a 32bit wallet too .
A 32 bit wallet would be nice for your info , some people only have a 32bit system such as me . And I was asking dev , not you for your info .
Maybe if he would answered from the get go it would have help . so back off me .
July 26, 2015, 12:31:40 AM
I successfully synced myself to the correct chain. I suggest deleting everything in ~/.axiom on linux, and clearing your Axiom folder in your AppData folder on Windows (except the wallet.dat).
Clearing those files allowed me to sync properly. Best of luck!
Clearing those files allowed me to sync properly. Best of luck!
na it is still forked lads who neveer closed their wallets are running their own chains. that is the reason deleting block data wont fix this issue. im afraid at present only relaunch will be the fix with proper nodes.
Well If there is a relaunch , maybe dev will put up a 32bit wallet too .
A 32 bit wallet would be nice for your info , some people only have a 32bit system such as me . And I was asking dev , not you for your info .
July 26, 2015, 12:30:50 AM
... need a relaunch
July 26, 2015, 12:30:15 AM
I successfully synced myself to the correct chain. I suggest deleting everything in ~/.axiom on linux, and clearing your Axiom folder in your AppData folder on Windows (except the wallet.dat).
Clearing those files allowed me to sync properly. Best of luck!
Clearing those files allowed me to sync properly. Best of luck!
na it is still forked lads who neveer closed their wallets are running their own chains. that is the reason deleting block data wont fix this issue. im afraid at present only relaunch will be the fix with proper nodes.
Well If there is a relaunch , maybe dev will put up a 32bit wallet too .
A 32 bit wallet would be nice for your info , some people only have a 32bit system such as me . And I was asking dev , not you for your info .
July 26, 2015, 12:29:31 AM
so can the dev upload the bootstrap to the proper chain? the thing syncs to a different fork on every new fresh chain
July 26, 2015, 12:27:38 AM
I think I am on the correct chain at 360 block.
First all my blocks dissapeared, then I restarted and
the block I got made the 30 confirms.
feel free to post a hash we can all confirm First all my blocks dissapeared, then I restarted and
the block I got made the 30 confirms.
July 26, 2015, 12:26:28 AM
How do I go about limiting the number of cores this uses? I don't want to run my cpu full throttle for this. Setgenerate true 2 does not work...
if setgenerate doesnt work you can set the # of cores in task manager via "affinity" Thanks. Learn something new everyday.
How? (I do it in Windows 7) Bring up your task manager (Ctrl+Alt+Del) and click on the processes tab. Then find your software name on the list. (must be running)
Then right-click it and select "Affinity" and then check only the cores you wish this software to use. You're done. Close Task Manager
July 26, 2015, 12:26:05 AM
I successfully synced myself to the correct chain. I suggest deleting everything in ~/.axiom on linux, and clearing your Axiom folder in your AppData folder on Windows (except the wallet.dat).
Clearing those files allowed me to sync properly. Best of luck!
Clearing those files allowed me to sync properly. Best of luck!
na it is still forked lads who neveer closed their wallets are running their own chains. that is the reason deleting block data wont fix this issue. im afraid at present only relaunch will be the fix with proper nodes.
Well If there is a relaunch , maybe dev will put up a 32bit wallet too .
July 26, 2015, 12:24:08 AM
I think I am on the correct chain at 360 block.
First all my blocks dissapeared, then I restarted and
the block I got made the 30 confirms.
First all my blocks dissapeared, then I restarted and
the block I got made the 30 confirms.
July 26, 2015, 12:22:40 AM
How do I go about limiting the number of cores this uses? I don't want to run my cpu full throttle for this. Setgenerate true 2 does not work...
if setgenerate doesnt work you can set the # of cores in task manager via "affinity" Thanks. Learn something new everyday.
July 26, 2015, 12:20:49 AM
relaunch please , this launching not smooth
July 26, 2015, 12:19:53 AM
I successfully synced myself to the correct chain. I suggest deleting everything in ~/.axiom on linux, and clearing your Axiom folder in your AppData folder on Windows (except the wallet.dat).
Clearing those files allowed me to sync properly. Best of luck!
Clearing those files allowed me to sync properly. Best of luck!
na it is still forked lads who neveer closed their wallets are running their own chains. that is the reason deleting block data wont fix this issue. im afraid at present only relaunch will be the fix with proper nodes.
Well If there is a relaunch , maybe dev will put up a 32bit wallet too .
July 26, 2015, 12:18:34 AM
I successfully synced myself to the correct chain. I suggest deleting everything in ~/.axiom on linux, and clearing your Axiom folder in your AppData folder on Windows (except the wallet.dat).
Clearing those files allowed me to sync properly. Best of luck!
Clearing those files allowed me to sync properly. Best of luck!
na it is still forked lads who neveer closed their wallets are running their own chains. that is the reason deleting block data wont fix this issue. im afraid at present only relaunch will be the fix with proper nodes.
July 26, 2015, 12:18:07 AM
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now.
The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
Diff is rising and we are adding two more strong nodes now.The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
i still fork with this nodes
OFFICIAL CHECKPOINTING NODES are on block 341. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!!
A 32bit wallet dev ?
July 26, 2015, 12:17:04 AM
A lot of forks are happening. Diff is rising and we are adding two more strong nodes now.
The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
Diff is rising and we are adding two more strong nodes now.The nodes are in the DNS seeding and you can manually add:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We will add 2 more servers quickly!
If you have any problem compiling, make install:
https://github.com/bitcoin/secp256k1
i still fork with this nodes
OFFICIAL CHECKPOINTING NODES are on block 379. If you aren't at this blockheight, close the wallet, open again, wait to resync. Our nodes are flooded with too many connections! New addnodes are coming!!
PRESS WINDOWS + R, ENTER:
notepad %APPDATA%/axiom/axiom.conf
ADD THIS TO THE FILE:
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
We're adding two more nodes now. Syncing is taking forever. If you have a node running with server=1 daemon=1 and youre around block 380, share your IP for addnode!
Jump to: