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

[verycoinsuchlist]

my wallets went offline for a short time as well ... I noted this just by the miner having rpc touble ... after 10-15 seconds it moved on... that happened around the height thecryptoworld is about right now... I'm reviewing the logfiles for something suspicious right now...


ok, pretty much sure, a fork has happened... yet, I'm not too sure about who's @ the right chain... I could bite myself for not being enough into the code in general, but I've got the hunch, that comparing blocktrust and trust around the height when some miner or pool finds itself being moving on a forked chain could contribute to eventually provide some clues...


hehe, someone's called his account 'pls_dont_fork' over at thecryptoworld... baaaaad omen dude


however, on 2 separate wallets each connected individually to mooo1 and mooo3 respectively, both seem to agree upon the height reflected by blockexperts explorer atm.

[1715446531]

1715446531

[1715446531]

1715446531

[1715446531]

1715446531

[1715446531]

1715446531

[AmberCoinDev]

The only difference between networks before and after hardfork is adding a "checkpoint=" line in .conf file on node01.
Before there was only 1 node that sometimes even has a downtime but network was still working!
Now 3 nodes and one of them is checkpointing server (node01)

Recently we have tried to remove that line from the .conf. This cause that all nodes were on different heights within an hour.
Now this line is back in .conf

As an experiment of POS only mode we can try to operate network without pool mining and even reduce a solo mining.
While turn on POS mining with the following .conf:

listen=1
rpcuser=user
rpcpassword=pass
rpcport=31981
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com
addnode=ambercoin03.mooo.com

All nodes will be restarted with bantime=1800 (30 min).

[bathrobehero]

my wallets went offline for a short time as well ... I noted this just by the miner having rpc touble ... after 10-15 seconds it moved on... that happened around the height thecryptoworld is about right now... I'm reviewing the logfiles for something suspicious right now...


ok, pretty much sure, a fork has happened... yet, I'm not too sure about who's @ the right chain... I could bite myself for not being enough into the code in general, but I've got the hunch, that comparing blocktrust and trust around the height when some miner or pool finds itself being moving on a forked chain could contribute to eventually provide some clues...


hehe, someone's called his account 'pls_dont_fork' over at thecryptoworld... baaaaad omen dude

If the UI on your pool is up to date then your pool is behind by 149 blocks compared to the mooo nodes. Funny thing is that I am connected to both the mooo nodes and your pool.

Edit:
getblockbynumber 610125
"flags" : "proof-of-stake",
"proofhash" : "00003e0f6a2fd81e66b911f3822556fea125461d6c9ff8715b0614983ec80cdf",

[AmberCoinDev]

getblockbynumber 610125
"proofhash" : "00003e0f6a2fd81e66b911f3822556fea125461d6c9ff8715b0614983ec80cdf"

Matches.

[verycoinsuchlist]

getblockbynumber 610125
"proofhash" : "00003e0f6a2fd81e66b911f3822556fea125461d6c9ff8715b0614983ec80cdf"

Matches.

here, too ... so thecryptoworld could be assumed to went offroad

As an experiment of POS only mode we can try to operate network without pool mining and even reduce a solo mining.
While turn on POS mining with the following .conf:

listen=1
rpcuser=user
rpcpassword=pass
rpcport=31981
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com
addnode=ambercoin03.mooo.com

All nodes will be restarted with bantime=1800 (30 min).

well, we'll see how thorough this experiment will turn out to be conductable... especially regarding the balance between low-diff-attraction vs. experimental-curiosity

but in general it might turn out to be a good idea, after all at least worth an attempt.

the reducing of the bantime in general is a good idea to get back on track faster if one finds itself stuck on a forked chain.

I'll open up one staking and one listening wallet again making the above modifications... but I think I will try one with moo1 & 2, another with moo3 as a starting node... might give some additional insight.

[5ick3uffalo]

27 days of Q4 ending

Maybe surprise our dividends arrive as x-mas present.

But i guess not happening


Wallet stuck again, lol.

Since 4 hours

[pokeytex]

27 days of Q4 ending

Maybe surprise our dividends arrive as x-mas present.

But i guess not happening


Wallet stuck again, lol.

Since 4 hours

Your not kidding...  I could really use that BTC for Christmas presents right about now!

[TimC]

27 days of Q4 ending

Maybe surprise our dividends arrive as x-mas present.

But i guess not happening


Wallet stuck again, lol.

Since 4 hours

I've been minting and staying on the correct chain with a simple .conf file

maxconnections=25
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com
addnode=ambercoin03.mooo.com

I'm not solo mining just mining and it seems the peers that are connected to me are mostly on the correct chain also. I think those trying 'connect' and only connecting to one peer are having connection problems. This is a peer to peer network. If you are not talking to your peers how to you think you are going to stay on the correct chain. I've been bouncing around from 17 to 2 connections but mostly around 7~9 connections. Hopefully all your forking settles down. Maybe if you have more peers it will help spread the load across the network. Instead of broadcasting your blocks all down one peer if you broadcasted you solution to 15+ peers maybe you will not fork as much since 15 peers will get you block at the same time to pass to other peers they are connected to. Otherwise trying to jam all traffic down one peer and that peer get full or congested that may cause you to fork off the one peer you are connect to. Remember 'peer to peer' and not all centralized into one node.

[antho281]

Hey all,
That's a fact, we forked during the night, that's weird...
It is corrected now. I'm going to check it all day long to be sure it doesn't fork again.

Not totally sure why it forked... Still had 5 peers (0.o)


EDIT : We are back on track!

[5ick3uffalo]

27 days of Q4 ending

Maybe surprise our dividends arrive as x-mas present.

But i guess not happening


Wallet stuck again, lol.

Since 4 hours

I've been minting and staying on the correct chain with a simple .conf file

maxconnections=25
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com
addnode=ambercoin03.mooo.com

I'm not solo mining just mining and it seems the peers that are connected to me are mostly on the correct chain also. I think those trying 'connect' and only connecting to one peer are having connection problems.

I`m connecting not only to one peer (same .conf and nodes as you) and have problems.

Right now i´m on the right chain

getblockbynumber 606621

"proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0"






All synced but all the stakes all orphaned.

[bathrobehero]

getblockbynumber 606621

"proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0"

Same.

[5ick3uffalo]

getblockbynumber 606621

"proofhash" : "00000000162bea0ef20d45a4b6038164c0c63eb0afc6a620f25ea8e79ae99df0"

Same.

Does yours stake normally?

I was setting up my wallet again, curious if my stakes are orpahned again (should know within 2 hours or so)

[Jayfek]

getblockcount
610837
getblockbynumber 610837
"proofhash" : "0000efdb3b8ccf386c2f6cac6ff53c7de61946f50ccf1cfd05b5a03d69fb05c2"

[antho281]

getblockcount
610837
getblockbynumber 610837
"proofhash" : "0000efdb3b8ccf386c2f6cac6ff53c7de61946f50ccf1cfd05b5a03d69fb05c2"

Matches!

[AmberCoinDev]

getblockcount
610837
getblockbynumber 610837
"proofhash" : "0000efdb3b8ccf386c2f6cac6ff53c7de61946f50ccf1cfd05b5a03d69fb05c2"

Matches.

[Slydrule]

27 days of Q4 ending

Maybe surprise our dividends arrive as x-mas present.

But i guess not happening


Wallet stuck again, lol.

Since 4 hours

I've been minting and staying on the correct chain with a simple .conf file

maxconnections=25
addnode=ambercoin01.mooo.com
addnode=ambercoin02.mooo.com
addnode=ambercoin03.mooo.com

I'm not solo mining just mining and it seems the peers that are connected to me are mostly on the correct chain also. I think those trying 'connect' and only connecting to one peer are having connection problems. This is a peer to peer network. If you are not talking to your peers how to you think you are going to stay on the correct chain. I've been bouncing around from 17 to 2 connections but mostly around 7~9 connections. Hopefully all your forking settles down. Maybe if you have more peers it will help spread the load across the network. Instead of broadcasting your blocks all down one peer if you broadcasted you solution to 15+ peers maybe you will not fork as much since 15 peers will get you block at the same time to pass to other peers they are connected to. Otherwise trying to jam all traffic down one peer and that peer get full or congested that may cause you to fork off the one peer you are connect to. Remember 'peer to peer' and not all centralized into one node.

So here is an example of what I was asking about.  This person has the 3 main nodes in his config file but he has 7-9 connections which means he is connecting to other peers besides the 3 main nodes.

This config file should include:

listen=0

and he should use connect=    instead of addnode=

maxconnections is superfluous since connecting to the 3 nodes with listen=0 will result in only 3 connections maximum.

What this tells me is that not everyone is following the instructions that have been posted.

What people need to understand is that during this situation more connections is not a good thing.  We want connections to be restricted to the main nodes only.

I understand that this may not solve the problem because there may be another problem in the wallet itself which is causing forks even when these nodes are connected exclusively.  But if we fix that problem we still may need to restrict peer connections to the main nodes for a while until the bad forks go away.

In the meantime, I started my wallet last night after forking connecting only to ambercoin01 and ambercoin03 and I have managed to stay on the right fork.  I am staking and solo mining.

[nara1892]

Wallet Amberstuck again,
the discussions on BTT only about networks,node,connections,conf.file,wallet ,..etc more than twenty pages without solutions
Dividends until now not happening,no news,no announcements
hi Dev : we are waiting your respons here about the dividends
please give you respect for those who waiting for

thanks

[5ick3uffalo]

For me, the dividend money is gone.

Everything else is surprise, i expect nothing.

[verycoinsuchlist]

...funny thing is, my solomining wallet stayed on track 'till now... the staking one went off, no connections (banned) as of now.

For me, the dividend money is gone.

Everything else is surprise, i expect nothing.

yup, same here... would be nice to inform the people about the delay, tho

but I think if this coin is going POS only due to 'dunno how to fix, so we close POW', I'm definitely out

[Abiky]

For me, the dividend money is gone.

Everything else is surprise, i expect nothing.

For the most part, I think that the reason Ambercoin has attracted many investors (from inside and outside the crypto world) has been its dividends payouts. If this would no longer happen, then I guess there would be lack of interest in the coin, and many people would dump Amber until it becomes a dead coin (I hope not). Lets be patient and wait a couple of more days. Perhaps, the dev is very busy and would tell us all about it before Xmas. I'm still holding my Amber here...