Looks good bro. Now I just need to wait an hour for these coins to mature.
Quote
However, you have to resend the transaction you sent after block 108881.
You know it!
Topic: [ANN] Triangles [TRI] Now Stable & Working Anonymous Cloak over TOR - ON BITTREX - page 21. (Read 90303 times)
August 29, 2014, 10:33:06 AM
Looks good bro. Now I just need to wait an hour for these coins to mature.
You know it!
August 29, 2014, 10:32:25 AM
That worked @ StephenJH? 
However, you have to resend the transaction you sent after block 108881.
However, you have to resend the transaction you sent after block 108881.
August 29, 2014, 10:18:52 AM
Quote
version after 108881, right?
correct
ok, then thats the cause. let me try to reproduce it...
yep. thats the reason.
Hint: If you used your wallet.dat with any previous released Cheops-Version its likely "corrupted". It crashes when it tries to stake then. If that happens:
Workaround:
1. start the wallet with "-stake=0"
2. dump privkey in console: "dumpprivkey
3. close the wallet.
4. rename the "triangles"-folder in %appdata%\roaming and keep it as a backup
5. create a new folder "triangles" in %appdata%\roaming
6. put the bootstrap dat there
7. start your wallet. after -2 mins a synced, clean wallet should come up
8. import your priv keys from step 2 via debug console: "importprivkey
Done, you now have a working wallet.
Edit: The two commands for debug console:
dumpprivkey
importprivkey
August 29, 2014, 10:17:29 AM
Quote
version after 108881, right?
correct
August 29, 2014, 10:16:52 AM
ok i'll do that,
side note: i started this one with stake=0 and it didn't crash
side note: i started this one with stake=0 and it didn't crash
probably because the wallet was used with other version after 108881, right? (so it contains data which doesnt fit to change parameters) see above.
privkey should work around that issue.
August 29, 2014, 10:15:01 AM
ok i'll do that,
side note: i started this one with stake=0 and it didn't crash and it's now synched
to start staking with the debug window what's the command?
side note: i started this one with stake=0 and it didn't crash and it's now synched
to start staking with the debug window what's the command?
August 29, 2014, 10:14:00 AM
-repairwallet kept it from crashing.
Then I synched and all was well but I had 1000 or so missing coins...
So I repairwallet'd again and I saw the whole "mismatched coins..." and the wallet then crashed.
Then I synched and all was well but I had 1000 or so missing coins...
So I repairwallet'd again and I saw the whole "mismatched coins..." and the wallet then crashed.
is that a wallet update of the block 10881-time? or did u use that wallet.dat with later releases? the latter, right?
ok, do the privkey thing please, i dont know why, but that wallet is somehow corrupted (for the client) thats something that should _always_ work.
August 29, 2014, 10:09:23 AM
-repairwallet kept it from crashing.
Then I synched and all was well but I had 1000 or so missing coins...
So I repairwallet'd again and I saw the whole "mismatched coins..." and the wallet then crashed.
Then I synched and all was well but I had 1000 or so missing coins...
So I repairwallet'd again and I saw the whole "mismatched coins..." and the wallet then crashed.
August 29, 2014, 09:54:51 AM
Good morning lol, yeah it still crashes on my win 8.1, seems like it crashes when staking kicks in. Is there a command to launch the wallet not staking?
edit should i try privkey?
edit should i try privkey?
that should work 100% as long as you have a clean running wallet. keep a backup as usual and try it.
try the "-repairwallet" switch first!
edit 2: "-stake=0" should disable staking. or "-reservebalance=100000".
edit 3: if u have a backup of your "triangles" folder from the 10881-blocks time: simply use it.
August 29, 2014, 09:40:58 AM
Good morning lol, yeah it still crashes on my win 8.1, seems like it crashes when staking kicks in. Is there a command to launch the wallet not staking?
edit should i try privkey?
edit should i try privkey?
August 29, 2014, 09:10:43 AM
Quote
...block 10977
I have a good feeling about this one.
I have a good feeling about this one.
I like it. Just woke up lol didn't TRI the privkey method. I'll just wait for your re-build... considering 10977.
We can't simply use the 10977 blocks chain due to the changes i made to the code. I forgot that for a minute, sorry. It wont get completely loaded with the current client, so lets try 108881 again.
We still have 2 other options though:
- I could create a bootstrap with 10916 blocks out of the 10977 blocks - we could work with that
- i could add a hard checkpoint in the sources so we could still use 10977. i will do that if we have no success with this try. when we have those 3-4 staking clients online again, things should just work out the same way they did with 10977 blocks chain. *fingers crossed*
August 29, 2014, 08:57:44 AM
Update again: Since strange crashes on win8 (only for some users) happened, clean rebuild.
Starting @ block 10881 once again (with an updated client - so you have to work with the bootstrap file here if you used yesterdays release!):
This update is mandatory! You have to update now!
This is an instant hard fork - there is no update height involved (because we would never reach it)!
New GitHub repository:
https://github.com/TrianglesCommunityProject/triangles
bootstrap.dat and peers.dat only (see below): https://mega.co.nz/#!5BsnRCRR!RkUsysowjxWmUmT8HjF-JgoRR-SIrOdBfMHpQVwe9qE
Wallets:
First make a backup of your wallet. Everyone should do that from time to time. Copy the "%appdata%\roaming\triangles" folder (Windows) to a safe place. Done.
WINDOWS wallet, v 3.4.3.1 "Cheops":
https://mega.co.nz/#!dUkW1TBY!tt7a9rVi4qhdkVi-LiT2MXdBTnV_XtLGmq3KGLlptZA
Included is a folder with a bootstrap.dat file with 10881 blocks (if you wallet isn't synced to 10881 blocks before you update OR IF YOU PREVIOUSLY USED YESTERDAYS RELEASE - see the included readme!). Also a folder with a peers.dat file (if you have trouble finding peers - see the readme!). This bootstrap.dat file is also useful if u just downloaded the wallet: create a folder "triangles" in %appdata%\roaming and place the bootstrap.dat into that folder - then start the wallet.
If u have coins in your wallet, please start your wallet with the "-connect=lkta5xj5nlnxxmrt.onion:24112" switch via commandline the first time after you updated your wallet. Its a non staking node and syncing to that node first prevents initial forking. Wouldn't be much of an issue if it happens though. This also helps if u have trouble getting a connection despite using the peers.dat (see above).
MAC wallet, wallet, v 3.4.3.1 "Cheops":
WE NEED SOMEONE WITH A MAC WHO VOLUNTEERS TO COMPILE IT!
TRI's main specifications:
X13 PoS over TOR
Coins in Circulation: ~49.5k
Annual interest: 33%
Coin Cap: 120k
Coin maturity: 7 blocks
Minimum stake age: 1 hour
Maximum stake age: 12 hours
Confirmations: 4
Tell me if problems arise - especially if your wallet crashes.
Starting @ block 10881 once again (with an updated client - so you have to work with the bootstrap file here if you used yesterdays release!):
This update is mandatory! You have to update now!
This is an instant hard fork - there is no update height involved (because we would never reach it)!
New GitHub repository:
https://github.com/TrianglesCommunityProject/triangles
bootstrap.dat and peers.dat only (see below): https://mega.co.nz/#!5BsnRCRR!RkUsysowjxWmUmT8HjF-JgoRR-SIrOdBfMHpQVwe9qE
Wallets:
First make a backup of your wallet. Everyone should do that from time to time. Copy the "%appdata%\roaming\triangles" folder (Windows) to a safe place. Done.
WINDOWS wallet, v 3.4.3.1 "Cheops":
https://mega.co.nz/#!dUkW1TBY!tt7a9rVi4qhdkVi-LiT2MXdBTnV_XtLGmq3KGLlptZA
Included is a folder with a bootstrap.dat file with 10881 blocks (if you wallet isn't synced to 10881 blocks before you update OR IF YOU PREVIOUSLY USED YESTERDAYS RELEASE - see the included readme!). Also a folder with a peers.dat file (if you have trouble finding peers - see the readme!). This bootstrap.dat file is also useful if u just downloaded the wallet: create a folder "triangles" in %appdata%\roaming and place the bootstrap.dat into that folder - then start the wallet.
If u have coins in your wallet, please start your wallet with the "-connect=lkta5xj5nlnxxmrt.onion:24112" switch via commandline the first time after you updated your wallet. Its a non staking node and syncing to that node first prevents initial forking. Wouldn't be much of an issue if it happens though. This also helps if u have trouble getting a connection despite using the peers.dat (see above).
MAC wallet, wallet, v 3.4.3.1 "Cheops":
WE NEED SOMEONE WITH A MAC WHO VOLUNTEERS TO COMPILE IT!
TRI's main specifications:
X13 PoS over TOR
Coins in Circulation: ~49.5k
Annual interest: 33%
Coin Cap: 120k
Coin maturity: 7 blocks
Minimum stake age: 1 hour
Maximum stake age: 12 hours
Confirmations: 4
Tell me if problems arise - especially if your wallet crashes.
August 29, 2014, 07:26:02 AM
Quote
...block 10977
I have a good feeling about this one.
I have a good feeling about this one.
I like it. Just woke up lol didn't TRI the privkey method. I'll just wait for your re-build... considering 10977.
August 28, 2014, 10:54:20 PM
ok...i will check that tomorrow - whatever that is.
One thing you could try: does it run in win 7 compatibilty mode?
Or you could simply import your private key(s) into the blank, working wallet:
- start original wallet without connections (so it doesnt crash - remove peers.dat)
- dump all private keys via console: dumpprivkey (repeat for all adresses u have in "receive" tab), copy the keys somewhere
- start up blank, new, synced wallet. import the keys via debug console: importprivkey
You would lose your unconfirmed transactions though. Those become visible again as soon as someone else who has them in his mempool confirms them (=mines a block. should happen within the next blocks - if not: resend them).
Worth a try, you cant lose anything if you keep a backup of your original folder.
Ok, out for a few hours now. Sleep! Finally...
Re:
Upcoming shortly:
- clean rebuild of the wallet (strange win8 starting issues for some ppl)
- starting off @ at yesterdays height until we got stuck again: block 10977 (maybe - it shouldn't but maybe - that also resolves the strange win8 issues). also the blockchain was quite lively then, it should move immediately!
I have a good feeling about this one.
One thing you could try: does it run in win 7 compatibilty mode?
Or you could simply import your private key(s) into the blank, working wallet:
- start original wallet without connections (so it doesnt crash - remove peers.dat)
- dump all private keys via console: dumpprivkey
- start up blank, new, synced wallet. import the keys via debug console: importprivkey
You would lose your unconfirmed transactions though. Those become visible again as soon as someone else who has them in his mempool confirms them (=mines a block. should happen within the next blocks - if not: resend them).
Worth a try, you cant lose anything if you keep a backup of your original folder.
Ok, out for a few hours now. Sleep! Finally...
Re:
Upcoming shortly:
- clean rebuild of the wallet (strange win8 starting issues for some ppl)
- starting off @ at yesterdays height until we got stuck again: block 10977 (maybe - it shouldn't but maybe - that also resolves the strange win8 issues). also the blockchain was quite lively then, it should move immediately!
I have a good feeling about this one.
August 28, 2014, 10:45:54 PM
yep, crashes as soon as it connects to the network windows 8.1
Yes, if i don't use my original wallet dat it connects and synchs without crashing.
Quote
but a clean wallet on win8 can connect and is synced?
Yes, if i don't use my original wallet dat it connects and synchs without crashing.
August 28, 2014, 10:45:36 PM
yes, if you delete all appdata (backup first!) and start new (i only tried with bootstrap) it will run.
August 28, 2014, 10:44:11 PM
i have no fucking clue whats going on.
lets try one thing until i simply recompile that wallet and double-check stuff. i havent changed anything that could possibly cause this.....
anyways.
please try this (keep backup as usual):
- close wallet.
- delete everything but wallet.dat from %appdata%\roaming\triangles - everything. all folders too!
- start the wallet.
- when its started, close it again
- put the bootstrap.dat into the folder
- start the wallet again
- should have 10881 blocks and no connections
- close the wallet
- start with "-connect=lkta5xj5nlnxxmrt.onion:24112"
does that work? if not - at which point does it crash?
edit: Oh ok only win8 pro.......in that case i will simply recompile the clean sources again tomorrow i guess. after double-checking
lets try one thing until i simply recompile that wallet and double-check stuff. i havent changed anything that could possibly cause this.....
anyways.
please try this (keep backup as usual):
- close wallet.
- delete everything but wallet.dat from %appdata%\roaming\triangles - everything. all folders too!
- start the wallet.
- when its started, close it again
- put the bootstrap.dat into the folder
- start the wallet again
- should have 10881 blocks and no connections
- close the wallet
- start with "-connect=lkta5xj5nlnxxmrt.onion:24112"
does that work? if not - at which point does it crash?
edit: Oh ok only win8 pro.......in that case i will simply recompile the clean sources again tomorrow i guess. after double-checking
The wallet will run all day with no connections. It will crash when started with -connect= as soon as it connects
but a clean wallet can connect and is synced?
August 28, 2014, 10:39:49 PM
i have no fucking clue whats going on.
lets try one thing until i simply recompile that wallet and double-check stuff. i havent changed anything that could possibly cause this.....
anyways.
please try this (keep backup as usual):
- close wallet.
- delete everything but wallet.dat from %appdata%\roaming\triangles - everything. all folders too!
- start the wallet.
- when its started, close it again
- put the bootstrap.dat into the folder
- start the wallet again
- should have 10881 blocks and no connections
- close the wallet
- start with "-connect=lkta5xj5nlnxxmrt.onion:24112"
does that work? if not - at which point does it crash?
edit: Oh ok only win8 pro.......in that case i will simply recompile the clean sources again tomorrow i guess. after double-checking
lets try one thing until i simply recompile that wallet and double-check stuff. i havent changed anything that could possibly cause this.....
anyways.
please try this (keep backup as usual):
- close wallet.
- delete everything but wallet.dat from %appdata%\roaming\triangles - everything. all folders too!
- start the wallet.
- when its started, close it again
- put the bootstrap.dat into the folder
- start the wallet again
- should have 10881 blocks and no connections
- close the wallet
- start with "-connect=lkta5xj5nlnxxmrt.onion:24112"
does that work? if not - at which point does it crash?
edit: Oh ok only win8 pro.......in that case i will simply recompile the clean sources again tomorrow i guess. after double-checking
The wallet will run all day with no connections. It will crash when started with -connect= as soon as it connects
August 28, 2014, 10:34:56 PM
i have no fucking clue whats going on.
lets try one thing until i simply recompile that wallet and double-check stuff. i havent changed anything that could possibly cause this.....
anyways.
please try this (keep backup as usual):
- close wallet.
- delete everything but wallet.dat from %appdata%\roaming\triangles - everything. all folders too!
- start the wallet.
- when its started, close it again
- put the bootstrap.dat into the folder
- start the wallet again
- should have 10881 blocks and no connections
- close the wallet
- start with "-connect=lkta5xj5nlnxxmrt.onion:24112"
does that work? if not - at which point does it crash?
edit: Oh ok only win8 pro.......in that case i will simply recompile the clean sources again tomorrow i guess. after double-checking
lets try one thing until i simply recompile that wallet and double-check stuff. i havent changed anything that could possibly cause this.....
anyways.
please try this (keep backup as usual):
- close wallet.
- delete everything but wallet.dat from %appdata%\roaming\triangles - everything. all folders too!
- start the wallet.
- when its started, close it again
- put the bootstrap.dat into the folder
- start the wallet again
- should have 10881 blocks and no connections
- close the wallet
- start with "-connect=lkta5xj5nlnxxmrt.onion:24112"
does that work? if not - at which point does it crash?
edit: Oh ok only win8 pro.......in that case i will simply recompile the clean sources again tomorrow i guess. after double-checking
August 28, 2014, 10:32:01 PM
nah my win 7 wallet is running and synced and it has a few transactions dated for the 28th
edit: no confirms on those transactions
edit: no confirms on those transactions
Mining, sending, or receiving?
yes, all
Oh, okay. I guess maybe it is something specifically with Windows 8 Pro. My Windows 8 64 standard version not crashing.
Jump to: