Re: [AXIOM] AxiomMemHash, Schnorr Sigs Implemented, APOS 3.0, AXH 2.0 Proposed

[Tortoise75]

   3+ days to re-download the BC   

Yes, that's why I didn't do it earlier

[1715441128]

1715441128

[groggin]

 i have 3 connections right now -



[
{
"addr" : "110.146.159.175:15760",
"addrlocal" : "72.74.138.99:60584",
"services" : "00000001",
"lastsend" : 1465537893,
"lastrecv" : 1465537894,
"bytessent" : 151168,
"bytesrecv" : 894048,
"conntime" : 1465480312,
"pingtime" : 0.87111100,
"version" : 60015,
"subver" : "/Origination:1.0.0/",
"inbound" : false,
"startingheight" : 850264,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "99.192.83.208:15760",
"addrlocal" : "72.74.138.99:59425",
"services" : "00000001",
"lastsend" : 1465537917,
"lastrecv" : 1465537917,
"bytessent" : 41330774,
"bytesrecv" : 2504167,
"conntime" : 1465527152,
"pingtime" : 356.95082700,
"pingwait" : 258.20778800,
"version" : 60015,
"subver" : "/Origination:1.0.6/",
"inbound" : false,
"startingheight" : 831385,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "94.41.175.187:15760",
"addrlocal" : "72.74.138.99:62624",
"services" : "00000001",
"lastsend" : 1465537923,
"lastrecv" : 1465537923,
"bytessent" : 230191760,
"bytesrecv" : 14621967,
"conntime" : 1465532645,
"pingtime" : 72.48170400,
"version" : 60015,
"subver" : "/Origination:1.0.0/",
"inbound" : false,
"startingheight" : 842583,
"banscore" : 0,
"syncnode" : false
}
]

  using the regular wallet, v1.0.0.0-g

this is my .conf

rpcuser=...
rpcpassword=...
rpcallowip=192.168.1.*
rpcport=6970
port=
gen=0
listen=1
server=1
addnode=104.236.231.72
addnode=45.55.172.95
addnode=174.127.110.41
addnode=162.222.181.215
addnode=93.157.25.130
addnode=104.236.231.72
addnode=158.181.253.55
addnode=187.74.206.189
addnode=72.92.19.54
addnode=24.56.61.247
addnode=89.212.140.63
addnode=46.101.23.149
addnode=68.41.180.163
addnode=46.72.126.178
addnode=193.198.102.32
addnode=161.53.40.94
addnode=192.52.166.80
addnode=104.238.133.29
addnode=197.89.64.51
addnode=122.107.182.65
addnode=82.236.68.185
addnode=5.9.72.102
addnode=212.45.26.38
addnode=104.238.133.29
addnode=197.89.64.51
addnode=104.197.49.247
addnode=104.197.64.168
addnode=130.211.74.245
addnode=104.155.34.235
addnode=107.167.189.225

[Tortoise75]

i cant get any connection with wallet.
I add node to config file and still no connections.
axioncoin.conf is like this:

[...]

I try with repairwallet in console command and i still dont get connected.
OS win 10, wallet ver. axiom-qt-staketest-optimized-staking-test2 1.0.0.0g
Any suggestion?

Additionally to what groggin already said: the config filename should be axiom.conf.

[keepall]

who is keeping this coin alive?

[twostepsally]

who is keeping this coin alive?

Don't know but the name and logo are great.

What a waste...

[buzztiaan]

wow yobit in maintainance for 8 days already, sad excuse for a exchange it is

[alexxynn]

Wallet on yobit again online. But he uses blockchain another than at me. The network has forked?

[Tortoise75]

Wallet on yobit again online. But he uses blockchain another than at me. The network has forked?

There are suspicions that some forking did happen. My resync proofed to be futile though, ended up with the same chain so I guess it's the mainnet. Yobits wallet does shows here a blocknumber 2-3 blocks lower than my wallet but a small test-tx went through without problems. So if it's only a little off try a very small amount to check things.

[alexxynn]

Wallet on yobit again online. But he uses blockchain another than at me. The network has forked?

There are suspicions that some forking did happen. My resync proofed to be futile though, ended up with the same chain so I guess it's the mainnet. Yobits wallet does shows here a blocknumber 2-3 blocks lower than my wallet but a small test-tx went through without problems. So if it's only a little off try a very small amount to check things.

I have the current block 862680, on yobit - 855457.

[groggin]

 i have # 862895   

[alexxynn]

Good Bye Axiom

[Tortoise75]

Oh dear, that's not good. Yobit and me match the first time I'm checking at #855562 right now. So there are at least 2 forks going.

[groggin]

Wallet on yobit again online. But he uses blockchain another than at me. The network has forked?

There are suspicions that some forking did happen. My resync proofed to be futile though, ended up with the same chain so I guess it's the mainnet. Yobits wallet does shows here a blocknumber 2-3 blocks lower than my wallet but a small test-tx went through without problems. So if it's only a little off try a very small amount to check things.

I have the current block 862680, on yobit - 855457.

^---= Today at 11:22:18 AM

i have # 862895   Smiley

  ^---=  Today at 03:44:30 PM


 this looks good to me

[Tortoise75]

Wallet on yobit again online. But he uses blockchain another than at me. The network has forked?

There are suspicions that some forking did happen. My resync proofed to be futile though, ended up with the same chain so I guess it's the mainnet. Yobits wallet does shows here a blocknumber 2-3 blocks lower than my wallet but a small test-tx went through without problems. So if it's only a little off try a very small amount to check things.

I have the current block 862680, on yobit - 855457.

^---= Today at 11:22:18 AM

i have # 862895   Smiley

 ^---=  Today at 03:44:30 PM


 this looks good to me

Not really, the upper time is his posting time of the block count, so it's 215 blocks in ~23 minutes, that's a bit many unless there was quite some delay between reading the block and posting.

Edit: Wait, different coin. This was a fast coin but I've forgotten how fast. What was the block time supposed to be?

[elbandi]

i have this:

Code:

# ./axiomhashd getblockhash 864362
09573fbb871921dc416403f8ff183291a03924c9d8a973fe8e697438ae82d4fb

[groggin]

i have this:

Code:

# ./axiomhashd getblockhash 864362
09573fbb871921dc416403f8ff183291a03924c9d8a973fe8e697438ae82d4fb

looks like we're good


10:13:08

getblockhash 864362


10:13:09

09573fbb871921dc416403f8ff183291a03924c9d8a973fe8e697438ae82d4fb

09573fbb871921dc416403f8ff183291a03924c9d8a973fe8e697438ae82d4fb
09573fbb871921dc416403f8ff183291a03924c9d8a973fe8e697438ae82d4fb

yup

showing blk# 864990 atm


10:17:55

getblockhash 864990


10:17:55

c46a36b5fbb822940270e7c88ad86d7bd7d981dd0c6311e90187a638fdb51aef

[alexxynn]

getblockhash 864362
09573fbb871921dc416403f8ff183291a03924c9d8a973fe8e697438ae82d4fb

getblockhash 864990
c46a36b5fbb822940270e7c88ad86d7bd7d981dd0c6311e90187a638fdb51aef


18:46:39

getblockhash 865170
18:46:39

d6366f6fccc30a416dfd509bcfce2cbdf89df53779f802c4bb97854c17fb9d60

[groggin]

nice, all agree


10:13:08

getblockhash 864362


10:13:09

09573fbb871921dc416403f8ff183291a03924c9d8a973fe8e697438ae82d4fb


10:17:55

getblockhash 864990


10:17:55

c46a36b5fbb822940270e7c88ad86d7bd7d981dd0c6311e90187a638fdb51aef


15:06:30

getblockhash 865170


15:06:30

d6366f6fccc30a416dfd509bcfce2cbdf89df53779f802c4bb97854c17fb9d60

[Tortoise75]

Well, I'm not on that fork for sure. My attempt to switch over didn't went further than the wallet re-scanning through that January bootstrap for the last hours so I don't know if that remotely works this time.

[groggin]

 my wallet is forking off again, appears that there is no longer enough hash to support the chain;

03:36:42

getmininginfo


03:36:42

{
"blocks" : 868495,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : {
"proof-of-work" : 0.00000012,
"proof-of-stake" : 298.99591880,
"search-interval" : 16
},
"blockvalue" : 250000000,
"netmhashps" : 0.00001236,
"netstakeweight" : 341130436771.26684570,
"errors" : "",
"pooledtx" : 0,
"stakeweight" : {
"minimum" : 440327998341,
"maximum" : 0,
"combined" : 440327998341
},
"stakeinterest" : 1000000,
"testnet" : false
}

 high PoS diff and getting about 1 blk/min.

going offline, it's been fun, shame on devs on vacation