[AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$

[Slydrule]

I have a question.  Is there a way to command the main nodes to unban clients that have been banned?  If we give our IP addresses can DEV unban us?  Sitting this out for the next 24 hours sucks.  Its the second time  for me in the last 4 days.

I set my CONF file to only connect to two of the three main nodes so that if I do get banned, I can re-connect to the other one.  Hopefully Dev can un-ban you though.

That's actually a good idea.

[antho281]

I have a question.  Is there a way to command the main nodes to unban clients that have been banned?  If we give our IP addresses can DEV unban us?  Sitting this out for the next 24 hours sucks.  Its the second time  for me in the last 4 days.

I set my CONF file to only connect to two of the three main nodes so that if I do get banned, I can re-connect to the other one.  Hopefully Dev can un-ban you though.

That's actually a good idea.

Were you connect to all three nodes?

[5ick3uffalo]

Ugh, 0 connections seems like i´m banned again.

Was on the 3 main nodes

Code:

send version message: version 90001, blocks=608793, us=0.0.0.0:0, them=45.32.69.218:31982, peer=45.32.69.218:31982
socket closed
disconnecting node ambercoin03.mooo.com
trying connection ambercoin02.mooo.com lastseen=0.0hrs
connection timeout
trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=608793, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
socket closed
disconnecting node ambercoin01.mooo.com
trying connection ambercoin02.mooo.com lastseen=0.0hrs
connection timeout
trying connection ambercoin03.mooo.com lastseen=0.0hrs
connected ambercoin03.mooo.com
send version message: version 90001, blocks=608793, us=0.0.0.0:0, them=45.32.69.218:31982, peer=45.32.69.218:31982
socket closed
disconnecting node ambercoin03.mooo.com
trying connection ambercoin02.mooo.com lastseen=0.0hrs
connection timeout
trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=608793, us=0.0.0.0:0, them=108.61.173.201:31982, peer=108.61.173.201:31982
socket closed
disconnecting node ambercoin01.mooo.com
trying connection ambercoin02.mooo.com lastseen=0.0hrs

[5ick3uffalo]

I have a question.  Is there a way to command the main nodes to unban clients that have been banned?  If we give our IP addresses can DEV unban us?  Sitting this out for the next 24 hours sucks.  Its the second time  for me in the last 4 days.

Why not just get an new IP-Adress (restarting router)

I just did, have 6 connections now but it won´t sync , stuck bec

Code:

02:30:35

getpeerinfo


02:30:35

[
{
"addr" : "104.131.230.130:31982",
"services" : "00000001",
"lastsend" : 1449192549,
"lastrecv" : 1449192551,
"conntime" : 1449192548,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 600436,
"banscore" : 0
},
{
"addr" : "76.113.218.139:31982",
"services" : "00000001",
"lastsend" : 1449192610,
"lastrecv" : 1449192618,
"conntime" : 1449192555,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 72764,
"banscore" : 0
},
{
"addr" : "144.76.238.2:31982",
"services" : "00000001",
"lastsend" : 1449192594,
"lastrecv" : 1449192619,
"conntime" : 1449192561,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 609386,
"banscore" : 0
},
{
"addr" : "108.61.173.201:31982",
"services" : "00000001",
"lastsend" : 1449192593,
"lastrecv" : 1449192619,
"conntime" : 1449192567,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 609388,
"banscore" : 0
},
{
"addr" : "85.25.214.214:31982",
"services" : "00000001",
"lastsend" : 1449192579,
"lastrecv" : 1449192580,
"conntime" : 1449192579,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 600775,
"banscore" : 0
},
{
"addr" : "96.2.34.208:31982",
"services" : "00000001",
"lastsend" : 1449192621,
"lastrecv" : 1449192622,
"conntime" : 1449192621,
"version" : 90001,
"subver" : "/AmberCoin:3.0.0.3/",
"inbound" : false,
"startingheight" : 609390,
"banscore" : 0
}
]

[Jayfek]

Hmm...
Misbehaving: 45.32.69.218:31982 (0 -> 100) DISCONNECTING
disconnecting node 45.32.69.218:31982
ERROR: ProcessBlock() : block with too little proof-of-stake
...and wallet dead.

[cidman]

new amber miner here
just started lil less than a week ago and thought id add what i did for my wallet
btw i have had no issues yet, wallet works perfect and im always the same as the new proofs
all i did was
download the new wallet and that bootstrap from a few pages back, install, close b4 syncing starts, then add bootstrap
make the conf with only moo1 and for me the solo mining settings and that upnp=0

server=1
daemon=1
listen=1
rpcuser=
rpcpassword=
rpcport=31981
upnp=0
connect=ambercoin01.mooo.com

hope this helps anyone new or older

[5ick3uffalo]

new amber miner here
just started lil less than a week ago and thought id add what i did for my wallet
btw i have had no issues yet, wallet works perfect and im always the same as the new proofs
all i did was
download the new wallet and that bootstrap from a few pages back, install, close b4 syncing starts, then add bootstrap
make the conf with only moo1 and for me the solo mining settings and that upnp=0

server=1
daemon=1
listen=1
rpcuser=
rpcpassword=
rpcport=31981
upnp=0
connect=ambercoin01.mooo.com

hope this helps anyone new or older

Tried exactly this some minutes ago

"repairwallet" after sync, so far so good.

[PowerHemp]

my wallet stop working since ~30min now.. dont sync since 30min and have now 0 connections

[5ick3uffalo]

my wallet stop working since ~30min now.. dont sync since 30min and have now 0 connections

You are most likely banned.

Get new IP Adress and try again:


download the new wallet and that bootstrap from a few pages back, install, close b4 syncing starts, then add bootstrap
make the conf with only moo1 and for me the solo mining settings and that upnp=0

server=1
daemon=1
listen=1
rpcuser=
rpcpassword=
rpcport=31981
upnp=0
connect=ambercoin01.mooo.com

[PowerHemp]

my wallet stop working since ~30min now.. dont sync since 30min and have now 0 connections

You are most likely banned.

Get new IP Adress and try again.

but why i got banned again? my wallet run before that fine

[5ick3uffalo]

my wallet stop working since ~30min now.. dont sync since 30min and have now 0 connections

You are most likely banned.

Get new IP Adress and try again.

but why i got banned again? my wallet run before that fine

Mine did run fine before,too for several days.

I don´t know the root of the problem.

I think no one knows until now.



Get new IP adress and then do same as described above.

[richwang]

27 days of Q4 ending

[verycoinsuchlist]

...wow, someone's throwing some stupendously large amount of hashrate @ the network  

{
  "blocks" : 609798,
  "currentblocksize" : 1000,
  "currentblocktx" : 0,
  "difficulty" : {
    "proof-of-work" : 17.70509657,
    "proof-of-stake" : 0.13281062,
    "search-interval" : 1
  },
  "blockvalue" : 50000000,
  "netmhashps" : 1901.07026879,
  "netstakeweight" : 10257231.96674271,
  "errors" : "",
  "pooledtx" : 0,
  "stakeweight" : {
    "minimum" : 982992,
    "maximum" : 0,
    "combined" : 982992
  },
  "testnet" : false
}

some like it hard...

[Slydrule]

I have a question.  Is there a way to command the main nodes to unban clients that have been banned?  If we give our IP addresses can DEV unban us?  Sitting this out for the next 24 hours sucks.  Its the second time  for me in the last 4 days.

I set my CONF file to only connect to two of the three main nodes so that if I do get banned, I can re-connect to the other one.  Hopefully Dev can un-ban you though.

That's actually a good idea.

Were you connect to all three nodes?

I was for a couple of days and everything was fine.  Then I noticed while solo mining the difficulty dropped under 1 which in the past has been a sure sign of a fork.  At that point I checked my connections and I was only connected to amber03.mooo.com.  I shut down my wallet, restored the database and restarted the wallet.  But then I got 0 connections and it has been that way for hours now.  I am not sure why 03 banned me after restoring the DB.

In any case this waiting 24 hours is excruciating.  I haven;t staked in 3 days either out of fear that staking was causing the wallets to fork.  But it appears I forked anyway so when I come back I intend to turn on staking too.

[AmberCoinDev]

Looking at the network behavior we consider a removing of POW mining completely to make the network stable.
Every time pool mining starts fork occurs.

[crzybilly]

Looking at the network behavior we consider a removing of POW mining completely to make the network stable.
Every time pool mining starts fork occurs.

if it is pool mining why not revert the change that is causing it? this didnt happen until fork.

additionally are you going to fix time warp bug? and latest db n openssl?

[verycoinsuchlist]

Looking at the network behavior we consider a removing of POW mining completely to make the network stable.
Every time pool mining starts fork occurs.

well, I'd say this is a mere guesswork... I myself had more of the impression that POS might be the issue of various forks poping into existence... there were pools running for hours stable 'til some network ripple caused a fork to happen and left them running on a bad chain... same goes for solomining, which happen to work pretty flawless sometimes for tens of hours... same goes for the block explorers which are not involved into mining at all (which I'd buntly assume here)... so, changing to POS only might just involves another planned hardfork without proof to actually yield the desired result, because of the actual problem not being nearly encircled as of now. if there'd be proof this being the issue, I'd eventually advocate this... but this sounds more like an experiment to me...


btw. the last one how probably bite the dust seems to be the thecryptoworld.org pool... I needed to reconnect my wallets to, but seem to be on the non-forked chain... but who might know

if it is pool mining why not revert the change that is causing it? this didnt happen until fork.
additionally are you going to fix time warp bug? and latest db n openssl?

+1

[bathrobehero]

I forked again. Solomining with only mooo1 which banned me.

As far as I know forks happen when blocks are generated from different sorces and those new blocks aren't make it to the whole network in time. And the fact that we fragment the network by only using connect/maxconnection and refusing other nodes to connect to us with listen=0 I don't think we will ever solve it this way.

With that said I think the best course of action would be if all of us would start generating blocks on the same node, meaning we should all mine on the same pool until we can interconnect all of our nodes. A pool that generates most of the blocks can't be thrown off by forked nodes as far as I know - unless something is really messed up. We should also only connect our wallets to the pool in order to make sure our wallets always get the newest blocks. For miners the dedicated nodes like the three mooo nodes doesn't really help with the forks because they aren't generating blocks just helping the communication between nodes but they do let you fork and ban you if you do because of solomining.

Since the cryptoworld pool solved 504 blocks in the last 24 hours it seems to be the biggest pool so now I'm only connected to it (connect=amber.thecryptoworld.org:4034) and will only mine there instead of solomining, BUT will re-enable PoS so if I get forked it will be safe to say it's because of PoS.

[verycoinsuchlist]

I forked again. Solomining with only mooo1 which banned me.

As far as I know forks happen when blocks are generated from different sorces and those new blocks aren't make it to the whole network in time. And the fact that we fragment the network by only using connect/maxconnection and refusing other nodes to connect to us with listen=0 I don't think we will ever solve it this way.

With that said I think the best course of action would be if all of us would start generating blocks on the same node, meaning we should all mine on the same pool until we can interconnect all of our nodes. A pool that generates most of the blocks can't be thrown off by forked nodes as far as I know - unless something is really messed up. We should also only connect our wallets to the pool in order to make sure our wallets always get the newest blocks. For miners the dedicated nodes like the three mooo nodes doesn't really help with the forks because they aren't generating blocks just helping the communication between nodes but they do let you fork and ban you if you do because of solomining.

Since the cryptoworld pool solved 504 blocks in the last 24 hours it seems to be the biggest pool so now I'm only connected to it (connect=amber.thecryptoworld.org:4034) and will only mine there instead of solomining, BUT will re-enable PoS so if I get forked it will be safe to say it's because of PoS.

there are as well forks happening by POS...

...and the pool @ thecryptoworld might have been forked as well... but it might as well be me, the blockexperts explorer and mooo1

and the thecryptoworld pool was the only pool being active for the last like 10 hours straigt alone and even longer in accompanyment with zpool when that pool forked eventually... and the hashrate was pretty constant... there were spikes of enormous POW hashrate in comparison but the network seemed to go through those events without any problem... which imho are all evidence contra POW being the issue here...

so, I'd really advocate for really finding the problem in the first place instead of switching to POS only just to 'try'...

[bathrobehero]

I forked again. Solomining with only mooo1 which banned me.

As far as I know forks happen when blocks are generated from different sorces and those new blocks aren't make it to the whole network in time. And the fact that we fragment the network by only using connect/maxconnection and refusing other nodes to connect to us with listen=0 I don't think we will ever solve it this way.

With that said I think the best course of action would be if all of us would start generating blocks on the same node, meaning we should all mine on the same pool until we can interconnect all of our nodes. A pool that generates most of the blocks can't be thrown off by forked nodes as far as I know - unless something is really messed up. We should also only connect our wallets to the pool in order to make sure our wallets always get the newest blocks. For miners the dedicated nodes like the three mooo nodes doesn't really help with the forks because they aren't generating blocks just helping the communication between nodes but they do let you fork and ban you if you do because of solomining.

Since the cryptoworld pool solved 504 blocks in the last 24 hours it seems to be the biggest pool so now I'm only connected to it (connect=amber.thecryptoworld.org:4034) and will only mine there instead of solomining, BUT will re-enable PoS so if I get forked it will be safe to say it's because of PoS.

there are as well forks happening by POS...

...and the pool @ thecryptoworld might have been forked as well... but it might as well be me, the blockexperts explorer and mooo1

Yeah, thecryptoworld seem to have issues as well. With the current difficulty and the pool's hashrate it should find roughly 2-3 blocks per minute yet it barely finds anything. Damn.