[ANN] Triangles [TRI] Now Stable & Working Anonymous Cloak over TOR - ON BITTREX

[MemoryShock]

Important question! A new TRI user, can they just run the latest wallet and sync the blockchain like normal or do they have to use the bootstrap??

I won't be able to download until tomorrow morning but that would be useful information since I do not have the old TRI wallet...

[1714848277]

1714848277

[1714848277]

1714848277

[1714848277]

1714848277

[1714848277]

1714848277

[croTek4]

Important question! A new TRI user, can they just run the latest wallet and sync the blockchain like normal or do they have to use the bootstrap??

I won't be able to download until tomorrow morning but that would be useful information since I do not have the old TRI wallet...

Yep, had you in mind for this question.

[wurstgelee]

You could do it without the bootstrap - but I wouldnt recommend it for 2 reasons:

- It takes WAAAAAYYY longer than to import the bootstrap and sync on from there.
- Syncing would probably stop at several points (probably @ 9000, 9500, 10000 blocks etc pp). Known issue with some parts of what I call the "crapchain"* but easy to bypass with the bootstrap file.


* main.h, line 31:

Code:

static const int CRAPCHAIN_CUTOFF_BLOCK = 17691; // pre-Pharao (version 4) blockchain until block 17691

PS: So as a summary for a new wallet.:

- Put the bootstrap.dat into %appdata%\roaming\triangles folder - create that folder if it doesnt exist (which is most likely)
- Start the wallet. It takes a a few mins (depending on your system speed) then your wallet comes up with an almost synced blockchain. It should automatically sync to the current block.

Thats it.

EDIT: yes, almost resting. having a smoke. then rest.

[MemoryShock]

Good to know...thanks guys!

Get some well deserved rest, WG...

[NightmareLev8]

Good work WurstGelee (or in german: Ich ziehe meinen Hut vor Dir.)
For real, this is amazing.

I will now try to sync my wallet and see if it works fine.
Another thing, is this repository https://github.com/TrianglesCommunityProject/triangles up-2-Date? (EDIT: It´s okay, I saw it in your post. )If so, I will try (in the next days) to compile the wallet on MacOS and maybe on a Pi.

btw. for the fun, the code for the faucet is also ready (maybe some last improvements). But it works great as I tested it with another coin daemon.
Also a nice price jump on bittrex which I saw on my new Android App:
https://i.imgur.com/pBEJ1j2.png?1

[wurstgelee]

Good work WurstGelee (or in german: Ich ziehe meinen Hut vor Dir.)
For real, this is amazing.

I will now try to sync my wallet and see if it works fine.
Another thing, is this repository https://github.com/TrianglesCommunityProject/triangles up-2-Date? (EDIT: It´s okay, I saw it in your post. )If so, I will try (in the next days) to compile the wallet on MacOS and maybe on a Pi.

btw. for the fun, the code for the faucet is also ready (maybe some last improvements). But it works great as I tested it with another coin daemon.
Also a nice price jump on bittrex which I saw on my new Android App:

Danke! Falls das nicht zu indiskret ist: Wo kommst du her? Hamburg hier.

And back to english:

That app looks great! I really like the orange-on-black color scheme. Also this brings up some questions:

- Will it be available in the App store?
- Did you ever think of making it a full blown TRI-trading app (via bittrex API keys)?



As for the game/faucet: Drop a line if you need hosting!


And more general: Network looks healthy and sane. Great!

I noticed some smaller bugs/things to improve, but nothing really serious. All GUI-related stuff (i.e. like proxy settings making no sense since the local TOR proxy port is currently hardcoded to 19099 and setting another one in the settings wouldn't work) so far.


Also I started "defragmenting" my inputs today. Since I was part of the "block-spamming-crew" in early september, I had more than 2000 inputs in one of my TRI addresses (can be seen in the "Send coins" tab if you activate coin control under Settings->Options->Display and go to "Send coins") . Since the number of inputs per block is limited (because the block size is limited), this would cause trouble if I wanted to send a larger amount of TRI from that address in one transaction. I imagine this condition would at least also apply to StephenJH and  most likely to some others. Also my  "fragmented inputs" address didn't stake as much as it should do. The cause for this is the same as described above - if you have thousands of inputs, only a limited amount of them are selected for creating a PoS block - also due to block size limitation.

So how to resolve this? It's simple but a little annoying:

Simply send those inputs to yourself! Select 100 inputs at a time (starting with the lowest ones) via coin control and send them as one transaction to some other TRI address you own (if you don't have one, create one in the very same wallet). Repeat until you are down to a reasonable amount of inputs.
You might have noticed that "zero or almost zero-reward block spamming" (so no more small inputs are created) stopped with yesterdays release, so this is a one-time task - this grade of fragmentation or vast amount of inputs won't occur again.


If the above text seems too muddle-headed to read and understand  -  say it. I am merely awake.


edit: As for the GitHub sources: I will most likely (most likely because I will have SEVERAL drinks tonight) upload the clean sources tomorrow. If not tomorrow, it will be Monday.

[wurstgelee]

This is me and someone else sanitzing inputs.

[NightmareLev8]

Danke! Falls das nicht zu indiskret ist: Wo kommst du her? Hamburg hier.

Ich komme aus Luxemburg, beherrsche aber die deutsche Sprache.

And back to english:

That app looks great! I really like the orange-on-black color scheme. Also this brings up some questions:

- Will it be available in the App store?

If it is desired, I will publish it in the PlayStore. Anyway I still need a dev-account to upload it, but this should not be a big problem.

- Did you ever think of making it a full blown TRI-trading app (via bittrex API keys)?

Yes I thought about it and for the reason that the app already uses the Bittrex API to get the market information, further improvements such as trading are possible.

[wurstgelee]

Danke! Falls das nicht zu indiskret ist: Wo kommst du her? Hamburg hier.

Ich komme aus Luxemburg, beherrsche aber die deutsche Sprache.

And back to english:

That app looks great! I really like the orange-on-black color scheme. Also this brings up some questions:

- Will it be available in the App store?

If it is desired, I will publish it in the PlayStore. Anyway I still need a dev-account to upload it, but this should not be a big problem.

- Did you ever think of making it a full blown TRI-trading app (via bittrex API keys)?

Yes I thought about it and for the reason that the app already uses the Bittrex API to get the market information, further improvements such as trading are possible.

Do it! Both!

[croTek4]

will definitely be defraggin later. many many tiny inputs. We've got a working coin guys!

[wurstgelee]

will definitely be defraggin later. many many tiny inputs. We've got a working coin guys!

Defragging worked great for me! I'm down to ~10% of the original inputs that particular address had - and it's staking a lot more now. Diff is rising as the amount of total coins staking increases.

And yes! It obviously works great (so far - never say never)!

[StephenJH]

All good in the hood. 5 inputs here...  

It has been a while since I used bold, red letters here. Now is the time.

TRI wallet update - Pharao release (Version 4.0.0.4)

- Please report any issues or bugs (and suggestions) in this thread! -

What's new?

- Refactored codebase
- QT5-based wallet
- Secure messaging over TOR
- Hardcoded seednode (no need for "-connect" or "-addnode" or downloading peers.dat)
- Working localisation/language files
- Coin control (enable it in options if u need/want it)

(list probably incomplete - will be completed later)


Downloads:

WINDOWS wallet, v 4.0.0.4 "Pharao":

MAC wallet, v 4.0.0.4 "Pharao" - SOON!

bootstrap.dat


How to use:


1.) Back up your wallet:

- Start the old TRI wallet and dump your keys private keys: Go into Debug console and type dumpprivkey <TRIaddress> for every TRI address you want to keep (=probably those which have coins in it.) Note those keys somewhere, they are all u need to restore your wallet in any case.
- Additionally copy the "%appdata%\roaming\triangles" folder (Windows) to a safe place.

2.) Upgrade your wallet:

- Delete everything but the wallet.dat in the "%appdata%\roaming\triangles" folder (keep the "onion" folder too if you want to keep your old TOR address).
- Place the downloaded bootstrap.dat in that folder.
- Start the new Triangles client and wait for it to import the bootstrap. This may take a while (so be patient! ) depending on the number of transactions you have (transactions include mining PoS blocks!). You can monitor progress in the debug.log file. Also your blk0001.dat constantly gains size until it has the same as the bootstrap file.
- Done.

In case you experience any problems (you shouldn't though) do the following:
- Delete everything in "%appdata%\roaming\triangles" (keep the "onion" folder if you want to keep your TOR address).
- Start the new wallet client.
- A new, clean wallet is created.
- It doesn't matter that your wallet isn't synced at that point - and no need to wait for it. Import every private key via "importprivkey <TRI privkey)" in the debug console (your TRI adresses won't appear under "Receive coins" until you restart the wallet, you see them in your address book until then)
- Close and start the wallet again. You adresses should now appear in the "Receive coins" tab. Close the wallet again (no need to wait for syncing!).
- Continue exactly as described above ("Upgrade your wallet").

Additonal notes:

- The wallet design is definitely a subject to change/improve. This doesn't require forking and will probably be released as a non mandatory update (when it's done).
- The reason why I reverted to 17691 blocks lies within the previous blockspamming. There were several TRI adresses with >10000 transactions in the blockchain @33xxx blocks. That vast amount caused trouble when operating those addresses with the wallet. The ~16000 blocks which were made "undone" shouldn't be a problem though: Most of those close-to-zero or zero reward blocks were generated by myself and StephenJH within 4 or 5 days. Bittrex disabled their wallet way before block 17691 so no coins are lost (except <10 TRI minted (overall) and maybe 100 or 200 coins sent to me from you guys. I can live with that!)
- To GitHub Repository isn't updated yet.  I will update GitHub sometimes that weekend after I beautified the code a little (mostly removing commented out code). In case you are suspicious and in anticipation of possible FUD: Bittrex won't reopen the wallet without up-to-date GitHub sources. Also the blockexplorer will tell you at any point that I didn't do anything malicious.  

(notes probably incomplete - will be completed later)

TRI's main specifications:

X13 PoS over TOR
- now with secure messaging -

Coins in circulation: ~49.6k
Annual interest: 33%
Coin Cap: 120k

Confirmations: 4
Coin maturity: 7 blocks
Minimum stake age: 1 hour
Maximum stake age: 12 hours
Block time: 120 secs

[croTek4]

PS: So as a summary for a new wallet.:

- Put the bootstrap.dat into %appdata%\roaming\triangles folder - create that folder if it doesnt exist (which is most likely)
- Start the wallet. It takes a a few mins (depending on your system speed) then your wallet comes up with an almost synced blockchain. It should automatically sync to the current block.

^^^for brand new TRI users

[StephenJH]

Wow what's up with the BTC bloodbath? Might buy a couple...

edit* oh yeah, TRI, TRI, and stuff.

[croTek4]

Yea, I'm at work and cant get anything done because my price alarms keep going off! i picked some more btc's up tho! You'd be a fool not to.

[wurstgelee]

Drinking.


Network weight +1000% in the last 12h. Diff +1000%. Looking good.

[StephenJH]

[wurstgelee]

Preparing sources for GitHub upload.

[wurstgelee]

Btw..time for some fork check:


If you type  

Code:

getblockhash 18770

into the debug console, it should return

Code:

0a324469bd61457982e1525c0ed81fd5f2cec70c64a73a905885fb8cc6fe7f63

.

if it doesn't, you are probably on a fork. if so simply close your wallet and start it with

Code:

triangles-qt.exe -connect=ubxidutptf2sslhq.onion

again.

close your wallet once synced to >18770 blocks and start it as usual.

if it doesn't sync that way, reload the bootstrap and sync from there with the "-connect" option as described above.


note: if you are on a fork, don't worry. this was rather likely to happen to someone when the blockchain was "restarted" with low diff and everyone joining with max stake weight.



edit: hm. "getpeerinfo" looks clean in a restarted wallet - it obviously held old info. so noone forked at all? even better.

[wurstgelee]

GitHub Repository updated!

910 Files committed.

https://github.com/TrianglesCommunityProject/triangles

Another thing, is this repository https://github.com/TrianglesCommunityProject/triangles up-2-Date?

It now is! Give it a shot!