Pages:
Author

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

hero member
Activity: 840
Merit: 500
Update: Had more to work @ work than i hoped for so i didn't manage to compile the win wallet yet.

On it now.

Edit: Ok, its compiling now, will take a while - didn't bother to assign more CPUs or RAM to the Vm. :|

Fingers crossed.

Edit 2: Something went wrong. Digging.

I wish you the best. I spent 8+ hours trying to setup a windows build environment and it still doesn't work :/

Ok, i gave up too. Will try again on sunday.
hero member
Activity: 742
Merit: 500
Running linux?


I created a test partion will try to compile it in debian now, let's see if it's mint's issue
member
Activity: 64
Merit: 10
hero member
Activity: 742
Merit: 500
Quote
You should update your openssl
member
Activity: 64
Merit: 10
member
Activity: 64
Merit: 10
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?
Code:
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.
hero member
Activity: 742
Merit: 500
hero member
Activity: 742
Merit: 500
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?
Code:
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
}
]
sr. member
Activity: 408
Merit: 250
ded
try deleting just your peers.dat and restarting the wallet now

deleted, no change:
Code:
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
}
]

hmm well both of your peers are at 10009 so maybe try resyncing again?
hero member
Activity: 742
Merit: 500
try deleting just your peers.dat and restarting the wallet now

deleted, no change:
Code:
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
}
]
sr. member
Activity: 408
Merit: 250
ded
try deleting just your peers.dat and restarting the wallet now
hero member
Activity: 742
Merit: 500
Still no change, stucked at 9003:
Code:
01:18:49
?
{
"blocks" : 9003,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 125.80864323,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 233937097,
"pooledtx" : 0,
"testnet" : false
}
hero member
Activity: 742
Merit: 500
hero member
Activity: 742
Merit: 500
if you compile yourself, edit version.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

I am compiling now with with min proto version 70101, let's see maybe you are right and it solves the problem.
hero member
Activity: 742
Merit: 500
sr. member
Activity: 408
Merit: 250
ded
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 version.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
hero member
Activity: 742
Merit: 500
All wallets after 3.3.3.3 are broken, switched now 3.3.3.3 again and it shows completly different information and doesn't pass 6508




after starting again 3.3.4.4


Seconds later I am on block 9027 and stucked again


And now no question marks anymore?:

hero member
Activity: 742
Merit: 500
DEV, WALLET DOES NOT SYNC!!!
hero member
Activity: 567
Merit: 502
Hey yo let's go
Pages:
Jump to: