Bitcoin Forum
May 24, 2024, 04:55:58 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 [3] 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 ... 149 »
  Print  
Author Topic: Re: [AXIOM] AxiomMemHash, Schnorr Sigs Implemented, APOS 3.0, AXH 2.0 Proposed  (Read 204910 times)
jasemoney
Legendary
*
Offline Offline

Activity: 1610
Merit: 1008


Forget-about-it


View Profile
July 26, 2015, 05:12:50 AM
 #41

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"

$MAID & $BTC other than that some short hodls and some long held garbage.
TimSweat
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250

TimSweat


View Profile
July 26, 2015, 05:13:04 AM
 #42

Need a 32 bit wallet please .

Lazada
Sr. Member
****
Offline Offline

Activity: 686
Merit: 250



View Profile
July 26, 2015, 05:13:36 AM
 #43

this right ?



{
"version" : "v1.0.0.0-g",
"protocolversion" : 60015,
"walletversion" : 60000,
"balance" : xxxxxxxxxx,
"newmint" : xxxxxxxxxx,
"stake" : 0.00000000,
"blocks" : 302,
"timeoffset" : 0,
"moneysupply" : 151000.00000000,
"connections" : 2,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : 0.00000440,
"proof-of-stake" : 0.00000000
},
"testnet" : false,
"keypoololdest" : 1437886320,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"errors" : ""
}
antonio8
Legendary
*
Offline Offline

Activity: 1386
Merit: 1000


View Profile
July 26, 2015, 05:15:47 AM
 #44

i show block 343

If you are going to leave your BTC on an exchange please send it to this address instead 1GH3ub3UUHbU5qDJW5u3E9jZ96ZEmzaXtG, I will at least use the money better than someone who steals it from the exchange. Thanks Wink
timertrainer
Full Member
***
Offline Offline

Activity: 135
Merit: 100


View Profile
July 26, 2015, 05:16:57 AM
 #45

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!

And how would you know that is the correct chain?  Roll Eyes

eh piss off lion go back to mcxnow

its correct because im not getting blocks every 5 seconds like i used to (and everyone else on a fork)
AxiomCryptocurrency (OP)
Newbie
*
Offline Offline

Activity: 42
Merit: 0


View Profile
July 26, 2015, 05:17:04 AM
Last edit: July 26, 2015, 05:35:52 AM by AxiomCryptocurrency
 #46

A lot of forks are happening.  Shocked 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!





TimSweat
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250

TimSweat


View Profile
July 26, 2015, 05:18:07 AM
 #47

A lot of forks are happening.  Shocked 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 ?

kevin1234a
Legendary
*
Offline Offline

Activity: 1162
Merit: 1000


Decentralizing Jesus on the Blockchain


View Profile WWW
July 26, 2015, 05:18:34 AM
 #48

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!

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.

TimSweat
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250

TimSweat


View Profile
July 26, 2015, 05:19:53 AM
 #49

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!

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 .

suprnova
Member
**
Offline Offline

Activity: 90
Merit: 10


View Profile
July 26, 2015, 05:20:49 AM
 #50

relaunch please , this launching not smooth
bones261
Legendary
*
Offline Offline

Activity: 1806
Merit: 1827



View Profile
July 26, 2015, 05:22:40 AM
 #51

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.
jimlite
Legendary
*
Offline Offline

Activity: 1848
Merit: 1018


View Profile WWW
July 26, 2015, 05:24:08 AM
 #52

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.

Binance, hottest/largest alt exchange, 2BTC daily no verification. https://www.binance.com/?ref=13309371
NEED TO RENT A RIG? All algos at http://www.miningrigrentals.com/register?ref=627


  ✵ Super FAST block times      ✵ Block Explorer right in the wallet!     ✵ Stealth Addresses     ✵ PoW/PoS hybrid  
██
██
██
██
██
██
██
██
██
██
██
Ancient Money
for a New World
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
██
Join the conversation!
██
██
██
██
██
██
██
██
██
██
██

                 ▄████▄▄    ▄
██             ████████████▀
████▄         █████████████▀
▀████████▄▄   █████████████
▄▄█████████████████████████
██████████████████████████
  ▀██████████████████████
   █████████████████████
    ▀█████████████████▀
      ▄█████████████▀
▄▄███████████████▀
   ▀▀▀▀▀▀▀▀▀▀▀

TWITTER


jasemoney
Legendary
*
Offline Offline

Activity: 1610
Merit: 1008


Forget-about-it


View Profile
July 26, 2015, 05:26:05 AM
 #53

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!

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 .
zero percent chance if the dev didnt make a 32 bit wallet at first that hes going to make one an hour after launch especially with the fork/sync issues people are experiencing. most cpu only coins are at a severe disadvantage when being mined on 32 bit vs 64 bit. so either wait for a server farm to release a legacy version or find something that suits your hardware better.

$MAID & $BTC other than that some short hodls and some long held garbage.
kevin1234a
Legendary
*
Offline Offline

Activity: 1162
Merit: 1000


Decentralizing Jesus on the Blockchain


View Profile WWW
July 26, 2015, 05:26:28 AM
 #54

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

jasemoney
Legendary
*
Offline Offline

Activity: 1610
Merit: 1008


Forget-about-it


View Profile
July 26, 2015, 05:27:38 AM
 #55

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

$MAID & $BTC other than that some short hodls and some long held garbage.
thelion07
Full Member
***
Offline Offline

Activity: 209
Merit: 100


View Profile
July 26, 2015, 05:29:31 AM
 #56

so can the dev upload the bootstrap to the proper chain? the thing syncs to a different fork on every new fresh chain
TimSweat
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250

TimSweat


View Profile
July 26, 2015, 05:30:15 AM
 #57

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!

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 .
zero percent chance if the dev didnt make a 32 bit wallet at first that hes going to make one an hour after launch especially with the fork/sync issues people are experiencing. most cpu only coins are at a severe disadvantage when being mined on 32 bit vs 64 bit. so either wait for a server farm to release a legacy version or find something that suits your hardware better.

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 .

xtrembash
Sr. Member
****
Offline Offline

Activity: 473
Merit: 250


View Profile
July 26, 2015, 05:30:50 AM
 #58

... need a relaunch

jasemoney
Legendary
*
Offline Offline

Activity: 1610
Merit: 1008


Forget-about-it


View Profile
July 26, 2015, 05:31:40 AM
 #59

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!

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 .
zero percent chance if the dev didnt make a 32 bit wallet at first that hes going to make one an hour after launch especially with the fork/sync issues people are experiencing. most cpu only coins are at a severe disadvantage when being mined on 32 bit vs 64 bit. so either wait for a server farm to release a legacy version or find something that suits your hardware better.

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 .
you asked 5 times, give it a rest.

$MAID & $BTC other than that some short hodls and some long held garbage.
TimSweat
Sr. Member
****
Offline Offline

Activity: 392
Merit: 250

TimSweat


View Profile
July 26, 2015, 05:34:14 AM
 #60

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!

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 .
zero percent chance if the dev didnt make a 32 bit wallet at first that hes going to make one an hour after launch especially with the fork/sync issues people are experiencing. most cpu only coins are at a severe disadvantage when being mined on 32 bit vs 64 bit. so either wait for a server farm to release a legacy version or find something that suits your hardware better.

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 .
you asked 5 times, give it a rest.

Maybe if he would answered from the get go it would have help . so back off me .

Pages: « 1 2 [3] 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 ... 149 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!