Pages:
Author

Topic: [ANN] Triangles [TRI] Now Stable & Working Anonymous Cloak over TOR - ON BITTREX - page 15. (Read 90274 times)

hero member
Activity: 840
Merit: 500

12:19:17

getblockhash 13732


12:19:17

26f7ee28013ddfa2603965a025d39d4ca80835819e058af7fc97ddb426ef1b01



12:19:54

getpeerinfo


12:19:54

[
{
"addr" : "127.0.0.1:54296",
"services" : "00000001",
"lastsend" : 1409501978,
"lastrecv" : 1409501978,
"conntime" : 1409500885,
"version" : 70203,
"subver" : "/Cheops:3.4.3.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 11801,
"banscore" : 0
},
{
"addr" : "127.0.0.1:54469",
"services" : "00000001",
"lastsend" : 1409501927,
"lastrecv" : 1409501877,
"conntime" : 1409501000,
"version" : 70203,
"subver" : "/Cheops:3.4.3.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 13713,
"banscore" : 0
},
{
"addr" : "127.0.0.1:55039",
"services" : "00000001",
"lastsend" : 1409501961,
"lastrecv" : 1409501961,
"conntime" : 1409501175,
"version" : 70203,
"subver" : "/Cheops:3.4.3.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 11596,
"banscore" : 0
},
{
"addr" : "vg7mkmcbbthtai64.onion:24112",
"services" : "00000001",
"lastsend" : 1409501926,
"lastrecv" : 1409501927,
"conntime" : 1409501300,
"version" : 70203,
"subver" : "/Cheops:3.4.3.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13716,
"banscore" : 1
},
{
"addr" : "127.0.0.1:55188",
"services" : "00000001",
"lastsend" : 1409501979,
"lastrecv" : 1409501979,
"conntime" : 1409501336,
"version" : 70203,
"subver" : "/Cheops:3.4.3.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 12354,
"banscore" : 0
},
{
"addr" : "127.0.0.1:55917",
"services" : "00000001",
"lastsend" : 1409501928,
"lastrecv" : 1409501928,
"conntime" : 1409501836,
"version" : 70203,
"subver" : "/Cheops:3.4.3.1/",
"inbound" : true,
"releasetime" : 0,
"startingheight" : 13728,
"banscore" : 0
},
{
"addr" : "fksblk3w6n7upske.onion:24112",
"services" : "00000001",
"lastsend" : 1409501928,
"lastrecv" : 1409501928,
"conntime" : 1409501842,
"version" : 70203,
"subver" : "/Cheops:3.4.3.1/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 13729,
"banscore" : 1
}
]


you are on a broken fork probably. check it by doing the using your own blk0001.dat  as bootstrap (after backup) - does it import to the end of the chain?
hero member
Activity: 1470
Merit: 521
No more Rekt and Bust
not i  Grin


11:45:18

getblockhash 12347


11:45:18

b241910b1243bd26c510c7ca4aabb38f74773a532b4cd39fbbf14d4a2ad90370 [both my clients]
hero member
Activity: 840
Merit: 500
Wurst, PM

Crap should be de-listed.... TRI is not crap.


ok - everyone: current block nr and hash of that block (getblockhash) please.

also peer address if u like. Smiley
hero member
Activity: 1470
Merit: 521
No more Rekt and Bust
Wurst, PM

Crap should be de-listed.... TRI is not crap.
sr. member
Activity: 882
Merit: 250
I noticed the de-listed warning is gone https://bittrex.com/Market/Index?MarketName=BTC-TRI

 Cool

what is wrong with bittrex , they are on de-listing spree.
hero member
Activity: 840
Merit: 500
figured that. could u make a copy of your blk001.dat and upload it?
hero member
Activity: 840
Merit: 500

getblockhash 12347

5ce4bc2588d0f75a51a1ef35627bf59679f53ece628120cbc1672a16f78b36e8


who else is on that chain?
newbie
Activity: 2
Merit: 0
hero member
Activity: 1470
Merit: 521
No more Rekt and Bust
legendary
Activity: 896
Merit: 1000
Also, does anyone know of someone reputable who can compile a Mac wallet for a small bounty?

Last thing, anyone who is going to be an active supporter, can you identify yourself?

I know wurstgelee, StephenJH, croTek4, whalebone, and I are in.

pineapples, gysca, Stenull, cynicSOB, romeshomey, tiggytomb, wadili89, Vlad2Vlad, CryptoHypno, irlandescoin, are you guys in?

Anyone else?

Hi,

First I am also in, which means I have a synced wallet (curr. block 13364). I synced it yesterday and checked the blockhashes posted in this thread, so yesterday I was on the right chain. I hope I still am...
Nevertheless I have a wallet with coins to stake (very small amount of 5.4 TRI's Tongue)

Second, if we get the chain now running smoothly and everyone is on the right chain I will setup a 24/7 node on a Rasperry Pi and write also a Tutorial for it.

Third I compiled the Mac Wallet yesterday morning, however I could not sync. So I have to investigate some time to delete the files (peer.data and so on as I already used the old versions on this Mac) and try to resync. But the compilation was successfull and I have a Mac Version of Cheops.

Finally, if everything runs smooth I have an idea to create a web-game (in some kind of betting/dice). This game will accept first only TRI (and later on other coins). Though this point depends first on the motivation of the community (but I already see that the right guys are involved Wink ) and personal motivation. Grin

So to answer your question, yes I am in.

Perfect!  Thanks for your support!
legendary
Activity: 896
Merit: 1000
My renamed blk001.dat starts me at 12273.
sr. member
Activity: 392
Merit: 250
the Cat-a-clysm.
great, let me check if that works for me. hang on a min

edit: could one of you give me a peer address to connnect to? that 12193 chain?

edit2: Oh, PM. thanks croTek4, checking it now



fksblk3w6n7upske.onion
newbie
Activity: 8
Merit: 0
I haven's seen anything new in the wallet
hero member
Activity: 840
Merit: 500
great, let me check if that works for me. hang on a min

edit: could one of you give me a peer address to connnect to? that 12193 chain?

edit2: Oh, PM. thanks croTek4, checking it now

hero member
Activity: 1470
Merit: 521
No more Rekt and Bust
Yes, did everything you said. synced to block 12190 immediately. restarted wallet and now its to block 12193

10:22:05

getblockhash 12193


10:22:05

6e34c6ccdf84638057025485cd184e6f0731edc5c0eced086e64e8e07df2c2d9


yep, i have 2 wallets on this chain
sr. member
Activity: 392
Merit: 250
the Cat-a-clysm.
Yes, did everything you said. synced to block 12190 immediately. restarted wallet and now its to block 12193

10:22:05

getblockhash 12193


10:22:05

6e34c6ccdf84638057025485cd184e6f0731edc5c0eced086e64e8e07df2c2d9

uploading file now
hero member
Activity: 840
Merit: 500
09:55:38

getblockhash 12190


09:55:38

73a6d294c97fbe4edfbbccfac3f189f6bf4d1e6e750aeaf303eac47ac7c83b86



12190 is the latest block it will sync to. my other wallet shows the same block hash but is synced to 13608 (haven't messed with that one since last update)

edit: have to use -connect= or else i dont get a connection. should i try importing peers.dat?


you did what i asked (clean triangles folder with your blk001.dat as bootstrap.dat) and it imported it up to block 12190? right away? or did it stop importing at some other point and afterwards synced to 12190?

anyways - you have a clean wallet which synced to 12190 - right? please upload that blk0001.dat of the clean wallet with 12190 somewhere and pm me the link! if thats true maybe no fixing sources is needed - only resyncing.  (and applying the fix later via update height) Smiley

sr. member
Activity: 392
Merit: 250
the Cat-a-clysm.
09:55:38

getblockhash 12190


09:55:38

73a6d294c97fbe4edfbbccfac3f189f6bf4d1e6e750aeaf303eac47ac7c83b86



12190 is the latest block it will sync to. my other wallet shows the same block hash but is synced to 13608 (haven't messed with that one since last update)

edit: have to use -connect= or else i dont get a connection. should i try importing peers.dat?
hero member
Activity: 840
Merit: 500
0 active connections for the wallet?

Have you tried starting wallet with "-connect=lkta5xj5nlnxxmrt.onion:24112"? once you do that and get wallet synced, then start wallet normally.

edit: so are we all on the wrong fork?

Basically - yes. Check it please, i need your help. Smiley

PS: that node will probably be down throughout the afternoon. expect the network to destabilize from now on to until release new wallets due to you guys testing (hopefully) and myself stopping/starting/resyncing nodes for testing. but thats  expected (thats why i say it now Smiley ) and nothing to worry about!
hero member
Activity: 840
Merit: 500
Good morning/afternoon/evening/night everyone. Smiley

So everything went smoothly the last 24h+ hours. Diff reached almost 0.003 (3e-3). Remember - we started @ 6e-8! Wink

Unfortunately we still have that bad block from when bittrex flooded the gates (=made a large amount of coins with max coinage available for staking @ once) so we will have to revert the chain to when that happened (11499/11500).

To verify that I need your help:

Please do the following (simple, safe and fast):

1. close your wallet, rename your triangles folder in %appdata%\roaming.
2. create a new, empty triangles folder in %appdata%\roaming, copy you blk0001.dat from your renamed triangles folder (step 1) into that new traingles folder. rename it to bootstrap.dat in that new folder.
3. start the client. it will create a new empty wallet which trys to import your blockchain as bootstrap.

Please report here how far that worked out for you (that blockchain importing). Also post the hash of that last block here (getblockhash in debug console)

4. close wallet, revert changes: delete the new triangles folder you created in step 2. rename your renamed original triangles folder back to "triangles". start the wallet.

This way we can determine which is the best chain and use it later today. I think we all have a valid chain until 11499/15000 though.

On schedule for today:

1. Check/determine best blockchain with your help - see above.
2. Implement code change, introduce a NODE_MIN_STAKING_INTERVAL which prevents "chain block spamming" (one node rapidly mints a series of blocks) and will reduce forking risk. side effect will be a reduced number of 0.00 reward blocks. We currently mine ~ 1400 blocks per day, so ~1 block per minute average (damn we are fast! Wink ) A NODE_MIN_STAKING_INTERVAL of 3 minutes wont slow down the network if it has at least 3 staking nodes then. Also maybe make clients wait that interval after startup to increase chances they are synced to the best chain - further reduces forking risk. Any thoughts on this? Does that make sense?
3. Thoroughly test changed code. If u see some clients with higher protocol version refusing connections in your debug log - thats probably me testing stuff. Smiley
4. Release wallets and bootstrap (with determined height - see step 1). I will sync at least 3 Nodes (2 wallets and the new 24/7 node for the block explorer) prior to that to make things easy.
5. Once network is stable, pick up block explorer work again.

Thats some work. It might be that some of it gets postponed to tomorrow. No false promises! Wink
 
Pages:
Jump to: