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

[StephenJH]

I very rarely use mintpal, haven't even logged in there in a month... or whenever the vericoin hack happened. I prefer Cryptsy & Trex.

So back on topic, 18 connections buddy. I'm bustin' it out...

[wurstgelee]

I don't use mintpal either.... so I'm not personally affected. Ridiculous nonetheless.



And I am impressed by those 18 connections as well. No forks. No sync issues. Nothing.

I did test everything as thoroughly as possible (a thing which moolah_io obviously didn't do), trying to simulate every condition that possibly could happen and which I could think of (and which I could test with a bunch of vms on my own)...it turned out to work even better than imagined. One shot, bullseye.  

Love it.

[NightmareLev8]

Regarding the Mac Wallet:

1. Download the Mac Wallet from here:
MAC wallet, v 4.0.0.4 "Pharao"
2. Download the bootstrap.dat from here:
bootstrap.dat
3. For security reason, backup your wallet (The wallet is located in ~/Library/Application Support/triangles/wallet.dat )
4. Delete the blk0001.dat and blkindex.dat in ~/Library/Application Support/triangles/
5. Copy the downloaded bootstrap.dat in ~/Library/Application Support/triangles/
6. Open the downloaded wallet with the command line "open triangles-qt.app --args -connect=ubxidutptf2sslhq.onion"
7. After the first sync you can start it normally without the "-connect=..." parameter.

I compiled it on Mavericks (10.9), tested it also on a clean Mavericks (10.9) and it worked. However this is no guaranty that it also works on other Mac-Versions. So if you have a problem with the wallet, please name the problem (as detailed as possible) and your current Mac-Version.

Regarding the Pi Wallet:

I compiled the wallet also on the Raspberry Pi with success, but if I execute the daemon I get the following error:
err] tor_assertion_failed_(): Bug: tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting.
err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at tor/memarea.c:127. Stack trace:
Aborted

The stack trace is indeed empty and no other error/warning is generated. Maybe someone has a hint for me what I can try, because I have no idea why the error occurs.

Regarding the faucet:

The faucet is now online: http://triangles.noip.me/Site/Faucet/
The current balance is around 2 TRI, which is enough for a couple of claims.
But why such low balance? As the faucet is currently in the testing phase.  
Therefore if you want a good faucet, it would be nice if you can test it. And obviously you can also post any request/improvement for the faucet.

[StephenJH]

Night sent you a couple transactions +180.

[wurstgelee]

Regarding the Mac Wallet:

I am currently @ wage slavery, so I will keep my answers short:

Awesome, great, fantastic! I will upload it to info.triangles.technology when I am home!

Regarding the Pi Wallet:

I compiled the wallet also on the Raspberry Pi with success, but if I execute the daemon I get the following error:
err] tor_assertion_failed_(): Bug: tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting.
err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at tor/memarea.c:127. Stack trace:
Aborted

The stack trace is indeed empty and no other error/warning is generated. Maybe someone has a hint for me what I can try, because I have no idea why the error occurs.

I face/faced exactly the same problem when I wanted to try to compile the daemon on the ubunto vm I use for crosscompiling the windows wallet. I investigated a little further and stopped at the point where I would have had to remove a lot of packages - simply because I didn't want to risk losing my crosscompile-abilities. I have strong reasons to believe that this is related to boost.

The stacktrace shows a little more on ubuntu:

Code:

root@ubuntu:/opt/trianglesd# ./trianglesd 
Oct 07 17:00:30.182 [err] tor_assertion_failed_(): Bug: tor/memarea.c:127: alloc_chunk: Assertion realign_pointer(res->next_mem) == res->next_mem failed; aborting.
Oct 07 17:00:30.183 [err] Bug: Assertion realign_pointer(res->next_mem) == res->next_mem failed in alloc_chunk at tor/memarea.c:127. Stack trace:
Oct 07 17:00:30.183 [err] Bug:     ./trianglesd() [0x806f7e3]
Oct 07 17:00:30.184 [err] Bug:     ./trianglesd() [0x8164e05]
Oct 07 17:00:30.184 [err] Bug:     ./trianglesd() [0x810ea67]
Oct 07 17:00:30.184 [err] Bug:     ./trianglesd() [0x810eb3d]
Oct 07 17:00:30.185 [err] Bug:     ./trianglesd() [0x815c1c7]
Oct 07 17:00:30.185 [err] Bug:     ./trianglesd() [0x8127131]
Oct 07 17:00:30.185 [err] Bug:     ./trianglesd() [0x81272b7]
Oct 07 17:00:30.186 [err] Bug:     ./trianglesd() [0x81277ad]
Oct 07 17:00:30.186 [err] Bug:     ./trianglesd() [0x81278e5]
Oct 07 17:00:30.186 [err] Bug:     ./trianglesd() [0x80a4415]
Oct 07 17:00:30.186 [err] Bug:     ./trianglesd() [0x80a8c1e]
Oct 07 17:00:30.187 [err] Bug:     ./trianglesd() [0x80a8fa2]
Oct 07 17:00:30.187 [err] Bug:     ./trianglesd() [0x8120d56]
Oct 07 17:00:30.187 [err] Bug:     ./trianglesd() [0x8121f8e]
Oct 07 17:00:30.187 [err] Bug:     ./trianglesd() [0x8284980]
Oct 07 17:00:30.187 [err] Bug:     /usr/lib/libboost_thread.so.1.48.0(+0xb1cc) [0xb76be1cc]  <----- !!!! BOOST! :)
Oct 07 17:00:30.187 [err] Bug:     /lib/i386-linux-gnu/libpthread.so.0(+0x6d4c) [0xb72d0d4c]
Oct 07 17:00:30.187 [err] Bug:     /lib/i386-linux-gnu/libc.so.6(clone+0x5e) [0xb70df9de]
Aborted (core dumped)

If I invoke  

Code:

sudo apt-get remove libboost*

it lists a lot two different Boost versions actually installed on that system (Version 1.46 and 1.48) - besides those which are not installed.

I suppose a fix would be to install boost 1.48 to another location than usual (iirc you can specify the install location with the "b2" command) and explicitly link to that location/version when building the daemon - or simply removing boost 1.46 and only installing 1.48.

edit: I double checked it - on the machine where the compiled daemon works, there are only boost 1.48 packages installed. on the non-working machine with the same issue as you described are 1.46 and 1.48 packages installed. Both are Ubuntu 12.04 LTS systems. If I were you, I would start searching there on your Pi.

Regarding the faucet:

The faucet is now online: http://triangles.noip.me/Site/Faucet/
The current balance is around 2 TRI, which is enough for a couple of claims.
But why such low balance? As the faucet is currently in the testing phase.  
Therefore if you want a good faucet, it would be nice if you can test it. And obviously you can also post any request/improvement for the faucet.

I love it!

First test was successful:

Code:

Congratulations! 
0.020 TRI are sent to the following address
TXc7mPCNFFpinDonuSH5PNVY9S8nBcvGQm

I will have a closer look later this evening.

[wurstgelee]

I added the Mac wallet to the download section of http://info.triangles.technology.

I also uploaded a new bootstrap (20225 blocks).



edit: The faucet - it's great! One thing: Maybe change the description of the  captcha textfield from "Enter captcha code..." to "Enter captcha result..." ?!

We now have more or less have like 5 "products" - the wallet, the homepage, the block explorer, the faucet and the android app (+a new ann thread once bittrex reopens the wallet).

Maybe it's about time to think about a unified color scheme and/or design ? CI and stuff.  



Any thoughts on that?

[StephenJH]

Faucet is pretty smooth. I got .05 :p

[wurstgelee]

[ot] another day - another scam. this time: GhostCoin. :|

[StephenJH]

Heh yeah, I got a few very cheap yesterday... guess I should have sold but I normally like to hold a coin longer than 16 hrs. lol.

[wurstgelee]

To keep everyone up to date:

I received a note from bittrex regarding upgrade of the TRI wallet: It's still scheduled, it only was postponed a little due to more urgent matters like GHOST scam/bug/exploit.

[NightmareLev8]

Night sent you a couple transactions +180.

Many thanks. I will use a part of it in the faucet, because I see more claims than I thought.

I face/faced exactly the same problem when I wanted to try to compile the daemon on the ubunto vm I use for crosscompiling the windows wallet. I investigated a little further and stopped at the point where I would have had to remove a lot of packages - simply because I didn't want to risk losing my crosscompile-abilities. I have strong reasons to believe that this is related to boost.

If I invoke  sudo apt-get remove libboost* it lists a lot two different Boost versions actually installed on that system (Version 1.46 and 1.48) - besides those which are not installed.

I suppose a fix would be to install boost 1.48 to another location than usual (iirc you can specify the install location with the "b2" command) and explicitly link to that location/version when building the daemon - or simply removing boost 1.46 and only installing 1.48.

edit: I double checked it - on the machine where the compiled daemon works, there are only boost 1.48 packages installed. on the non-working machine with the same issue as you described are 1.46 and 1.48 packages installed. Both are Ubuntu 12.04 LTS systems. If I were you, I would start searching there on your Pi.

I gave it a try. I removed now every boost packages and indeed there were different versions installed. Now only the 1.48 is installed and the wallet is compiling again. But this will take a while. 

...textfield from "Enter captcha code..." to "Enter captcha result..." ?!

Done.
Regarding the color scheme. I don't know but I like the black and orange style. The same for the coinlogo, I think it looks great in orange.
Yes, I know that the boxes on the faucet are yellow. But when we have an unified scheme i will style it "correctly".
Now I am happy that the faucet is running smooth and is accepted by the community. Of course the faucet is not final.

[wurstgelee]

Night sent you a couple transactions +180.

Many thanks. I will use a part of it in the faucet, because I see more claims than I thought.

I face/faced exactly the same problem when I wanted to try to compile the daemon on the ubunto vm I use for crosscompiling the windows wallet. I investigated a little further and stopped at the point where I would have had to remove a lot of packages - simply because I didn't want to risk losing my crosscompile-abilities. I have strong reasons to believe that this is related to boost.

If I invoke  sudo apt-get remove libboost* it lists a lot two different Boost versions actually installed on that system (Version 1.46 and 1.48) - besides those which are not installed.

I suppose a fix would be to install boost 1.48 to another location than usual (iirc you can specify the install location with the "b2" command) and explicitly link to that location/version when building the daemon - or simply removing boost 1.46 and only installing 1.48.

edit: I double checked it - on the machine where the compiled daemon works, there are only boost 1.48 packages installed. on the non-working machine with the same issue as you described are 1.46 and 1.48 packages installed. Both are Ubuntu 12.04 LTS systems. If I were you, I would start searching there on your Pi.

I gave it a try. I removed now every boost packages and indeed there were different versions installed. Now only the 1.48 is installed and the wallet is compiling again. But this will take a while.  

...textfield from "Enter captcha code..." to "Enter captcha result..." ?!

Done.
Regarding the color scheme. I don't know but I like the black and orange style. The same for the coinlogo, I think it looks great in orange.
Yes, I know that the boxes on the faucet are yellow. But when we have an unified scheme i will style it "correctly".
Now I am happy that the faucet is running smooth and is accepted by the community. Of course the faucet is not final.

I'm looking forward to hear about the the outcome with the PI.

Black and orange would be fine for me as well. We would need some additional colors to get a complete scheme to work with though, but that shouldn't be too hard. There are enough tools for that, ie http://paletton.com.

Once we agree on a scheme I would put myself to work again, probably starting with something simple and fun - like the block explorer. Wallet would probably be next.

I would like to hear some additional feedback on that topic.  

PS: Maybe I sound like a broken record - but I really like the faucet. It's way more interesting than a simple "enter your address, get some coins"-faucet!

edit:

Code:

Congratulations! 
0.010 TRI are sent to the following address
TXc7mPCNFFpinDonuSH5PNVY9S8nBcvGQm

[StephenJH]

Good news wurst, yeah I bet trex is busy. The wait is killing me though... You guys give me hope for the alt crypto world yet.

I like clean, white bg, corporate looking stuff... I love the logo as is, simplicity rocks. Though I guess it could have a final sheen added to it. If 3angle did the art in the op he's obviously talented[not to mention the idea of tri].

[wurstgelee]

Good news wurst, yeah I bet trex is busy. The wait is killing me though... You guys give me hope for the alt crypto world yet.

I like clean, white bg, corporate looking stuff... I love the logo as is, simplicity rocks. Though I guess it could have a final sheen added to it. If 3angle did the art in the op he's obviously talented[not to mention the idea of tri].

To clarify: The logo itself stays, no arguing about that. Its only about unified colors for wallet, faucet, block explorer, homepage etc pp!  Corporate identity!

PS: Yeah..waiting is hard. Anticipation ffs.

[StephenJH]

Have an MEC wallet? [that would be a slick direction]

[wurstgelee]

Have an MEC wallet? [that would be a slick direction]

No, but I should probably get hold of one to see. Gonna do that tomorrow, it's late.

[croTek4]

Yes Trex!!! here come my TRIs!
ps So now that we are fully functional again, should we create a new ANN thread?

[NightmareLev8]

Bittrex wallet is online! I already started withdrawing
http://explorer.triangles.technology/chain/Triangles?count=20

Nice to hear. However I am stuck with the the Pi wallet. I tried now to build libboost (1.48) from source and installed it in a different location. Also I linked it explicit to these libs and deleted every old libboost*-packages. But it still gives me the assertion failure.

[croTek4]

something going on? both of my wallets have switched to "not staking" and it says last received block 29 minutes ago.
edit, still says not staking, but now it has one new block

[NightmareLev8]

something going on? both of my wallets have switched to "not staking" and it says last received block 29 minutes ago.

As I wanted to write that I can confirm this, a new block appeared. So on my side everything is fine.