 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
Same   You should update your openssl  |
|
|
|
try deleting just your peers.dat and restarting the wallet now
deleted, no change: .... hmm well both of your peers are at 10009 so maybe try resyncing again? I will give it now a last try but wallet or network is just broken. I am resyncing since couple of days, curious that dev is not answering. Is there anyone who can delete all data and resync again? No answers to that question until now. So whats broken, wallet net or chain? 01:23:07
?
getmininginfo
01:23:07
?
{
"blocks" : 9003,
"currentblocksize" : 0,
"currentblocktx" : 0,
"difficulty" : 125.80864323,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 233937097,
"pooledtx" : 0,
"testnet" : false
}
01:23:30
?
getpeerinfo
01:23:30
?
[
{
"addr" : "4mmbxrdk5xorxq4s.onion:24112",
"services" : "00000001",
"lastsend" : 1406330600,
"lastrecv" : 1406330600,
"conntime" : 1406330572,
"version" : 70101,
"subver" : "/Illuminatus:3.3.4.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 10008,
"banscore" : 1
},
{
"addr" : "fzwpi2uqgauy225m.onion:24112",
"services" : "00000001",
"lastsend" : 1406330592,
"lastrecv" : 1406330592,
"conntime" : 1406330576,
"version" : 70101,
"subver" : "/Illuminatus:3.3.4.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 10009,
"banscore" : 1
}
] Neither are broken. You're having an isolated problem with your wallet. |
|
|
|
Yes I did, many times. Version 3.3.3.3 syncs to block 9165, 3.3.4.3 to 1025, 3.3.4.4 to 9020.
When version 3.3.4.3 came out, I wanted to try it and wanted to see if sync is working properly. I deleted all data, started wallet and since then it did not work. I left the wallet for more than 24 hours version 3.3.4.3 open and nothing. Today I compiled new version 3.3.4.4, still does not work. Running peerinfo I can see than all peers do have version 3.3.3.3.
If new versions are broken, why are broken version posted untested? Is there anyone who can resync completly with 3.3.4.4?
I'm fully synced with 3.3.4.4 Could you try to delete all data except your wallet and resync? these are what I'm connected to now, after deleting everything.  [ { "addr" : "fzwpi2uqgauy225m.onion:24112", "services" : "00000001", "lastsend" : 1406327624, "lastrecv" : 1406327614, "conntime" : 1406327550, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "4mmbxrdk5xorxq4s.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327623, "conntime" : 1406327556, "version" : 70101, "subver" : "/Illuminatus:3.3.4.4/", "inbound" : false, "releasetime" : 0, "startingheight" : 9984, "banscore" : 1 }, { "addr" : "sv44mb2qcyxfwnbw.onion:24112", "services" : "00000001", "lastsend" : 1406327615, "lastrecv" : 1406327616, "conntime" : 1406327570, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 }, { "addr" : "6kickq6scfajdhot.onion:24112", "services" : "00000001", "lastsend" : 1406327679, "lastrecv" : 1406327680, "conntime" : 1406327679, "version" : 70099, "subver" : "/Pyramid:3.3.3.3/", "inbound" : false, "releasetime" : 0, "startingheight" : 9002, "banscore" : 1 } ] those two that are running 3.3.3.3 are messing with the network. if you compile yourself, edit protocol.h, change min proto version so its the same as the network protocol version. Then recompile. This will not allow older version to connect to you Thanks for suggestion, but if that would be the problem, then version 3.3.4.4 would not stuck, as there are peers with same version, my peers are not much different than yours 00:49:41
?
[
{
"addr" : "4mmbxrdk5xorxq4s.onion:24112",
"services" : "00000001",
"lastsend" : 1406328129,
"lastrecv" : 1406328433,
"conntime" : 1406328129,
"version" : 70101,
"subver" : "/Illuminatus:3.3.4.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 9984,
"banscore" : 1
},
{
"addr" : "lig5vcicm6hgjggx.onion:24112",
"services" : "00000001",
"lastsend" : 1406328133,
"lastrecv" : 1406328136,
"conntime" : 1406328132,
"version" : 70099,
"subver" : "/Pyramid:3.3.3.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 9002,
"banscore" : 1
},
{
"addr" : "sr77eqw7cxkc34zy.onion:24112",
"services" : "00000001",
"lastsend" : 1406328540,
"lastrecv" : 1406328173,
"conntime" : 1406328137,
"version" : 70099,
"subver" : "/Pyramid:3.3.3.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 6508,
"banscore" : 1
},
{
"addr" : "mcf4bxy7ksfl2jce.onion:24112",
"services" : "00000001",
"lastsend" : 1406328433,
"lastrecv" : 1406328397,
"conntime" : 1406328142,
"version" : 70099,
"subver" : "/Pyramid:3.3.3.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 6508,
"banscore" : 1
},
{
"addr" : "ufoi7dt2lv575nlh.onion:24112",
"services" : "00000001",
"lastsend" : 1406328417,
"lastrecv" : 1406328162,
"conntime" : 1406328158,
"version" : 70099,
"subver" : "/Pyramid:3.3.3.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 9002,
"banscore" : 1
},
{
"addr" : "qsjqt5tpcx7qsqfy.onion:24112",
"services" : "00000001",
"lastsend" : 1406328398,
"lastrecv" : 1406328415,
"conntime" : 1406328162,
"version" : 70099,
"subver" : "/Pyramid:3.3.3.3/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 9002,
"banscore" : 1
},
{
"addr" : "66pgszhqlte4u5n3.onion:24112",
"services" : "00000001",
"lastsend" : 1406328454,
"lastrecv" : 1406328537,
"conntime" : 1406328452,
"version" : 70101,
"subver" : "/Illuminatus:3.3.4.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 9027,
"banscore" : 1
},
{
"addr" : "ywedag3i2e3ocvel.onion:24112",
"services" : "00000001",
"lastsend" : 1406328477,
"lastrecv" : 1406328479,
"conntime" : 1406328477,
"version" : 70101,
"subver" : "/Illuminatus:3.3.4.4/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 9027,
"banscore" : 1
}
]
hmm. I am syncing fine, but I see that you're having problems. We'll work through this  You know why. |
|
|
|
stuck at 9003, i deleted all files at triangles folder but start reload the blocks again
but still at 9003
Can you try doing: Help -> Debug window -> Console -> Type in "getpeerinfo" and post the output here The problem may be that your client is not connecting with peers, so I'm looking to see if you have "Banscore=1" for all peers with all blocks. |
|
|
|
mac wallet stuck : 9003 block  Did you download the latest mac wallet (update last night)? i download a wallet who somebody posted here. v3.3.4.4 that is the last one? Yes, that should be the correct wallet. Hm, I am not having any problems with the mac wallet. Try restarting. If you continue to have problems, let me know, and I will try to diagnose your problem when I am home. |
|
|
|
mac wallet stuck : 9003 block Did you download the latest mac wallet (update last night)? |
|
|
|
|
Staking more coins...
You know why.
|
|
|
|
|
I'm downloading qt-sdk / updating macports to compile the wallet with new updates, but I'm about to go out to dinner. Someone should beat me to it.
You know why.
|
|
|
|
If i understood this right, we need a staking wallet to get the blockchain moving. We obviously have none currently -> MAC wallets not staking, win wallets not existing/also not staking, so no PoS blocks, no movement. Do we need to convince bittrex or some pool (which still has coins in wallet) to put some of their coins on stake? Other ideas? PS: If anybody here has a compiled, working wallet with coins in it: Bring it online! PPS: Or am i wrong? Right now I am experiencing problems syncing. After looking at the debug log and RPC:getpeerinfo it seems that this is due to faulty connections to .onion peers to download the remaining blocks. It is possible that this is because I am currently on a hospital WIFI with restricted access, so I will try again at a different location. Some additional notes: If you look at RPC:getpeerinfo, you will see that many peers have 9002 blocks (fully synced) which is good. What I believe is the problem right now is not enough staking peers connecting to the network. That said, I have bought all of the TRI that I can, but am unfortunately poor and ran out of BTC  This coin had a very good launch. Dev is quirky (in a fun way), but seems to be active. This network difficulties that we're having right now is an easy repair. We simply need: 1. More peers with 9002 blocks connecting so that we can all sync (alternatively, if someone with 9002 blocks could upload their blk0001.dat, we could fix this by loading with triangles-qt -loadblock="path to blk0001.dat") 2. More wallets containing coins fully synced Following this, proper PoS minting will occur. What happened is that when PoW ended and PoS was meant to begin, not enough synced wallets were staking. In the PoW phase, miners were competing for blocks. In this new PoS phase, wallets with staking coins compete for blocks in a lottery like system where the probability of a wallet to "earn" the right to mint a block is a function of (coin age)(coin size). As soon as we have enough stakers synced, this will continue. tl;dr: everything is going to be ok; dev doesn't seem to be AWOL; if I had more BTC I would still be buying. Hope this helps! |
|
|
|
scam
why
Sell me your coins. You know why. |
|
|
|
|
I'm seeing multiple peers on the network right now with 9002 blocks...
You know why.
|
|
|
|
I've been doing some reading on PoS and some debugging from console and RPC... 99% sure that 3angle is messing with you guys. I'm still buying TRI on Bittrex |
|
|
|
Anyone want to join in with me to offer a donation for compiled windows wallet?
I'm on mac, but we should get a windows wallet compiled.
no point in that as long as the blockchain is stuck. http://rentmydns.com:2750Isn't it possible that the blockchain is stuck because not enough coins are staking? |
|
|
|
|
Anyone want to join in with me to offer a donation for compiled windows wallet?
I'm on mac, but we should get a windows wallet compiled.
|
|
|
|
once PoW is over, and you all have dumped everything, when the marked is dead, and all hope seems lost.
Someone will buy every single coin from every one of you and set the price at the top of the pyramid.
You know why. Well if the wallet isn't working the only tri for sale are the ones already on the exchange.  Ironically, I had staked my coins to avoid panic selling  |
|
|
|
scam or not, I wont be parting with my triangles at this price  I'm along for the ride.  |
|
|
|
once PoW is over, and you all have dumped everything, when the marked is dead, and all hope seems lost.
Someone will buy every single coin from every one of you and set the price at the top of the pyramid.
You know why.
You know why. |
|
|
|
|
Perhaps someone with a large amount of coins stopped staking...
You know why.
|
|
|
|
|
you two need to talk and work it out.
you know why.
|
|
|
|
|
