Author

Topic: [AMBER] X13 POW/POS| 10k AMBER=0,01% SHARES | BUY, HOLD & GET DIVIDENDS in BTC/$ - page 125. (Read 407572 times)

member
Activity: 89
Merit: 10
no way i'm turning listen to 1 or using addnode instead of connect any time soon... after the last change, this led to 3 times forking as the mooo node frequently dropped the connection for a short time. so the slightest network jitter only led to either becoming banned, becoming connected to single clients still/again running on the wrong chain, or connected to clients with a blockheight far below the current one (no idea if those did or did not fork way earlier).

whatever change you made recently doesn't seem to be helpful, at least on my end... and I really do have other things in mind than bootstrapping those wallets over and over and over again... so I let you guys experiment if you will... with my wallets being offline I'm at least not taking part in the problem...

good luck, however
hero member
Activity: 630
Merit: 500
1. Download latest DB https://www.dropbox.com/s/rk4n2i1rppmmwwo/AmberCoin_0512.rar?dl=0
2. Delete peers.dat
3. Use this .conf to sync correctly:


Code:
listen=0
connect=ambercoin01.mooo.com

4. When wallet is synced turn it off.
5. Change .conf to:


Code:
listen=1
addnode=ambercoin01.mooo.com

6. Start wallet again.
7. Turn on POS minting


[]
{
"hash" : "00000000ba9206fcae6bba3f626e1e794457b82dae34019284dce0b3abe96c22",
"confirmations" : 2,
"size" : 213,
"height" : 613084,
"version" : 6,
"merkleroot" : "edfc8bd5447862398fd61cb3a5d31c92711eb8a998a529705f2ee474b466e027",
"mint" : 0.50000000,
"time" : 1449322809,
"nonce" : 8083322,
"bits" : "1d00c8ee",
"difficulty" : 1.27405809,
"blocktrust" : "14629f1ec",
"chaintrust" : "54176625ae2180",
"previousblockhash" : "45b43486aa4b23db15c1a75800006b6dfddc65eaad874a1809c8fa0937edcf4e",
"nextblockhash" : "3c39e19b069697e86e47207dc653cf45953b8f74bb534eb88f083d46e518cf48",
"flags" : "proof-of-work stake-modifier",
"proofhash" : "00000000ba9206fcae6bba3f626e1e794457b82dae34019284dce0b3abe96c22",
"entropybit" : 0,
"modifier" : "f567cb18471aabe2",
"modifierchecksum" : "7347a5fd",
"tx" : [
"edfc8bd5447862398fd61cb3a5d31c92711eb8a998a529705f2ee474b466e027"
]
}
hero member
Activity: 630
Merit: 500
1. Download latest DB https://www.dropbox.com/s/rk4n2i1rppmmwwo/AmberCoin_0512.rar?dl=0
2. Delete peers.dat
3. Use this .conf to sync correctly:


Code:
listen=0
connect=ambercoin01.mooo.com

4. When wallet is synced turn it off.
5. Change .conf to:


Code:
listen=1
addnode=ambercoin01.mooo.com

6. Start wallet again.
7. Turn on POS minting
member
Activity: 89
Merit: 10
great scott ...what's just going on with that unimaginably fucked up network... I'm really loosing it soon  Angry hrmpf...
sr. member
Activity: 703
Merit: 250
We have removed "checkpoint=" line from the .conf on node01.
Nodes02 and 03 are turned off.

Please download latest DB https://www.dropbox.com/s/rk4n2i1rppmmwwo/AmberCoin_0512.rar?dl=0
After you sync remove all "connect" lines before start to mine/stake
And restart your wallets.


you should unban people from node1

All should be unbanned already.

appears not

trying connection ambercoin01.mooo.com lastseen=0.0hrs
connected ambercoin01.mooo.com
send version message: version 90001, blocks=612693, us=ipaddress:31982, them=108.61.173.201:31982, peer=108.61.173.201:31982
socket closed
disconnecting node ambercoin01.mooo.com
member
Activity: 89
Merit: 10
very brittle network atm...

the 1 connection drops every now and then... I'm using connect instead of addnode again as the wallets probability to fork immediately jumps up when the mooo1 node disconnects even for a short time... found myself 2 times forking away the last 30mins and clinging to peers with way lower startingheight. ...with connect only, it at least tries to keep in touch with the mooo1 node only...

unbanned myself via new ip... the wallets went into ban within minutes
hero member
Activity: 630
Merit: 500
We have removed "checkpoint=" line from the .conf on node01.
Nodes02 and 03 are turned off.

Please download latest DB https://www.dropbox.com/s/rk4n2i1rppmmwwo/AmberCoin_0512.rar?dl=0
After you sync remove all "connect" lines before start to mine/stake
And restart your wallets.


you should unban people from node1

All should be unbanned already.
sr. member
Activity: 703
Merit: 250
We have removed "checkpoint=" line from the .conf on node01.
Nodes02 and 03 are turned off.

Please download latest DB https://www.dropbox.com/s/rk4n2i1rppmmwwo/AmberCoin_0512.rar?dl=0
After you sync remove all "connect" lines before start to mine/stake
And restart your wallets.


you should unban people from node1
hero member
Activity: 630
Merit: 500
[]
{
"hash" : "0000000071799a3f94bf7bc44ee04c93ce2944e7fee01232675a32a58cc7cca9",
"confirmations" : 1,
"size" : 186,
"height" : 612798,
"version" : 6,
"merkleroot" : "59ef0eb78cf678d53fdc630b3013dda84b9d26f37a1cd6731a5ca2593420157b",
"mint" : 0.50000000,
"time" : 1449314671,
"nonce" : 1938861146,
"bits" : "1d009446",
"difficulty" : 1.72651351,
"blocktrust" : "1b9fe8429",
"chaintrust" : "5416925a1ac418",
"previousblockhash" : "000000005ef49717ed6d20402f4a587d67182cb60f6217f2aa48527648a6e300",
"flags" : "proof-of-work",
"proofhash" : "0000000071799a3f94bf7bc44ee04c93ce2944e7fee01232675a32a58cc7cca9",
"entropybit" : 1,
"modifier" : "021a3278d9c7f131",
"modifierchecksum" : "15779c05",
"tx" : [
"59ef0eb78cf678d53fdc630b3013dda84b9d26f37a1cd6731a5ca2593420157b"
]
}
hero member
Activity: 630
Merit: 500
We have removed "checkpoint=" line from the .conf on node01.
Nodes02 and 03 are turned off.

Please download latest DB https://www.dropbox.com/s/rk4n2i1rppmmwwo/AmberCoin_0512.rar?dl=0
After you sync remove all "connect" lines before start to mine/stake
And restart your wallets.
member
Activity: 89
Merit: 10
ambercoin02.mooo.com and ambercoin03.mooo.com have lost sync with ambercoin01.mooo.com regardless that they were interconnected to each other with "connect".
We have shut them down for a while.



which my staking wallet used to escape on a fork... rolling back to my latest snapshot now.
...the mining wallet however is still online and in sync as it seems

blockexperts is most probably stuck as well... yet thecryptoworld is still running fine as far as I can tell

ok, now the mining wallet forked as well... only 1 connect to whoever 144.76.238.2 is... but obviously not on the right track... remember that this ip turned up in my log as 'misbehaving' because of too low pos diff...

Quote
12/05/15 09:20:07 Misbehaving: 144.76.238.2:31982 (0 -> 100) DISCONNECTING
12/05/15 09:20:07 disconnecting node 144.76.238.2:31982
12/05/15 09:20:07 ERROR: ProcessBlock() : block with too little proof-of-stake

methinks it might be more likely there's some issue with POS after all...

also I wouldnt wonder if it turns out this might be the last man standing... the darn low diff currently at thecryptoworld seems spurious, too

...did i just take over the network?? Huh Shocked Grin ...no risk, no fun  Cheesy
hero member
Activity: 630
Merit: 500
We are now investigating why that have happened and considering further steps to fix the problem.

Node01 now is on 612462 height.
hero member
Activity: 630
Merit: 500
ambercoin02.mooo.com and ambercoin03.mooo.com have lost sync with ambercoin01.mooo.com regardless that they were interconnected to each other with "connect".
We have shut them down for a while.

hero member
Activity: 630
Merit: 500
Didn't someone get busted by the SEC for "selling amber" this past week...good luck with this

As far as we can understand you are talking about GemCoin.
full member
Activity: 185
Merit: 100
Didn't someone get busted by the SEC for "selling amber" this past week...good luck with this
The SEC busted a pyramid scheme that involved false claims about amber mining.  The company involved was taking money from investors claiming they would make money from an amber mining operation but in fact they were paying the first investors out the money invested by later investors. There were no profits from amber mining or even an amber mining operation.  This has nothing to do with Ambercoin and its association with an amber  mining operation.
member
Activity: 89
Merit: 10
Didn't someone get busted by the SEC for "selling amber" this past week...good luck with this

evidence, or it didn't happen... Roll Eyes
hero member
Activity: 518
Merit: 505
Didn't someone get busted by the SEC for "selling amber" this past week...good luck with this
legendary
Activity: 994
Merit: 1000
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...  Smiley

Yeah, was the #1 reason i bought Ambercoin.

I find it little bit unfair because the ANN-topic says "BUY, HOLD & GET DIVIDENDS in BTC/$"

That´s missleading investors because not happening and should be removed imaho.


Wallet stuck again, omg i let it closed now until a fix is out.




sr. member
Activity: 289
Merit: 250
Yes, looks good.... same hash here!  Smiley
hero member
Activity: 605
Merit: 500

12:17:35

getblockbynumber 612135


12:17:35

{
"hash" : "0000000009f6d73e06ff83823ceee8f4182deedf6971339c92229e77b420a052",
"confirmations" : 1,
"size" : 247,
"height" : 612135,
"version" : 6,
"merkleroot" : "09bc8d8d9cdad4f4b5cc75805a4373fc602f3188fd5260dd26ba171935f76845",
"mint" : 0.50000000,
"time" : 1449288973,
"nonce" : 4828812,
"bits" : "1c147820",
"difficulty" : 12.50638105,
"blocktrust" : "c81aeb1f0",
"chaintrust" : "54149646a0895e",
"previousblockhash" : "0000000019fc6da6a383e5ac3799fad75a21b57c9968e350bf8eb728c5ffb1eb",
"flags" : "proof-of-work",
"proofhash" : "0000000009f6d73e06ff83823ceee8f4182deedf6971339c92229e77b420a052",
"entropybit" : 0,
"modifier" : "ec87fc0c3b7f2311",
"modifierchecksum" : "0718507c",
"tx" : [
"09bc8d8d9cdad4f4b5cc75805a4373fc602f3188fd5260dd26ba171935f76845"
]
}
Jump to: