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

[StephenJH]

 

Moneysupply[sometime] Aug. 31 : 49597.51493800
Moneysupply right now: 49603.34306100

Giggidy.

[wurstgelee]

Yes, the network is running smooth as far as I can tell.
Also I like the idea with the playgrounds. In that way everyone can contribute something (skills, ideas, etc.).
I played today also a bit on my playground and I developed a simple game idea.

The idea is the following:
First you have X unknown cards, for example 25 unknown cards.
One card (I will call it Jackpot-Card) has an adjustable value of TRI, for example 5 TRI.
The other 24 cards are all traps.
The game consists now by guessing under which card the 5 TRI are hidden.
Each time the user guesses he pays a fixed amount of TRI.
If the guess was successful, the users gets the 5 TRI (added to his balance) and a new game starts.
If the guess was a fail, the guessed card is "out of the game" and the game continues with a card less.

Some aspects to mention:

• A simple account system is needed, only username, password and email (optional)
• Everyone gets the same game, so it's a community game.
• I have a concept to make the game "cheat-proof" from the server side. Such that the Jackpot-Card is already known at the beginning of the game but not in plain-text. After each game the secrets are published. In that way the users can check every game for its correctness.

As I said it is a very simple game, but a Nice-To-Have. Maybe some other games can be added in the future.
And if the game drops some profit, this profit can be used for further works (Faucets, Development and so on).
So, what thinks the community about it?

Some screens:

I love the idea of having a game. Although i think you're thinking maybe way to complicated for a first step.

How about a simple, modified faucet (with gaming factor)?:

- 3 instead of 24 cards, 1 Jackpot card with fixed amount, maybe 1 TRI.
- maybe 1 Pick per IP and 1 (3?, 5?, 8?) hour
- if user picks right cards, he gets send TRI to the address he entered in some formfield prior to picking a card
- no account system, user only enters TRI address (we love anonymity! )

Since money (TRI ) is involved, it would have to be secure - "provably fair", so the right pick has to be known to the server in advance.

What do you think, could you create such a thing and what would you need? (A server with a running wallet would be no problem. Also a database. What else?)

PS: Thats Javascript I suppose/hope?

[NightmareLev8]

I love the idea of having a game. Although i think you're thinking maybe way to complicated for a first step.

How about a simple, modified faucet (with gaming factor)?:

- 3 instead of 24 cards, 1 Jackpot card with fixed amount, maybe 1 TRI.
- maybe 1 Pick per IP and 1 (3?, 5?, 8?) hour
- if user picks right cards, he gets send TRI to the address he entered in some formfield prior to picking a card
- no account system, user only enters TRI address (we love anonymity!)

I like the simplified idea as a kind of faucet.

Since money (TRI) is involved, it would have to be secure - "provably fair", so the right pick has to be known to the server in advance.

Yes, I am aware of this.
This is what I mean with "Cheat-Proof". I will try to integrate a system, where the correctness can be prooven without disclosing the right pick.

What do you think, could you create such a thing and what would you need? (A server with a running wallet would be no problem. Also a database. What else?)
PS: Thats Javascript I suppose/hope?

I can create such a faucet with a gambling factor. What I need is a running wallet, a database, server-side scripts and client-side scripts (Yes, Javascript).
So everything what is needed for a normal WebApp (except the wallet). But I already worked with the wallet over RPC, so this should not be a problem.
I will develop this faucet first on my playground and later some Beta-Tester are needed. How and where this faucet is hosted can later be clarified.

[smokeybehr]

I'm not sure what's going on, and this is the first time I've encountered this.

I'm connected to the network with 7 peers, but nothing is synchronizing. I get the same set of error messages in the log over and over:

Code:

received block d06a6412b9e8e0e0e584
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block d06a6412b9e8e0e0e584ffa69dd6a1979060288646ee482f6037625b575a5a8b

The block number is the only thing that changes. The "blocks remaining" keeps incrementing, and it never syncs up.

I've tried the fresh start; I've tried connecting to the lxta5 address, and letting it run; It's currently running with the "-stake=0' switch, and the same thing happens every time.

[NightmareLev8]

I'm not sure what's going on, and this is the first time I've encountered this.

I'm connected to the network with 7 peers, but nothing is synchronizing. I get the same set of error messages in the log over and over:

Code:

received block d06a6412b9e8e0e0e584
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block d06a6412b9e8e0e0e584ffa69dd6a1979060288646ee482f6037625b575a5a8b

The block number is the only thing that changes. The "blocks remaining" keeps incrementing, and it never syncs up.

I've tried the fresh start; I've tried connecting to the lxta5 address, and letting it run; It's currently running with the "-stake=0' switch, and the same thing happens every time.

Which wallet and which version are you using?

[pseudonymdude]

I'm not sure what's going on, and this is the first time I've encountered this.

I'm connected to the network with 7 peers, but nothing is synchronizing. I get the same set of error messages in the log over and over:

Code:

received block d06a6412b9e8e0e0e584
ERROR: CheckProofOfStake() : INFO: read txPrev failed
WARNING: ProcessBlock(): check proof-of-stake failed for block d06a6412b9e8e0e0e584ffa69dd6a1979060288646ee482f6037625b575a5a8b

The block number is the only thing that changes. The "blocks remaining" keeps incrementing, and it never syncs up.

I've tried the fresh start; I've tried connecting to the lxta5 address, and letting it run; It's currently running with the "-stake=0' switch, and the same thing happens every time.

Time to bring everyone to the right chain:

If  "getblockhash 12460" in the debug console doesnt give you this output you're not on the right chain: 4df338563eb017db366be9568e9595f8e2b18580fe0d361db4022ad8c6add694.

So, how to get there with a really clean wallet and a really clean blockchain file in a really easy way?

1. In your currently running wallet go to debug console and do a "dumpprivkey <TRIaddress>" for every address you have in the "Receive"-Tab (you can spare those which have no coins and which you dont want to keep.). Note those private keys in some txt file.
2. Close wallet. Rename the %appdata%\roaming\triangles folder and keep it as a backup.
3. Create a new, empty "triangles" folder in %appdata%\roaming. Drop only this bootstrap there, nothing else: https://mega.co.nz/#!RZVDhDia!XHDCWzUpMEzZTkU30ll5zGGIT_peBdj9TvFs3DgmTgs (after you extracted it from the zip archive)
4. Start the wallet (takes a while - it imports the blockchain from bootstrap). Use "-connect=ubxidutptf2sslhq.onion:24112" at first run (Its the 24/7 node which will be the block explorer) and let it sync - you now have the cleanest of all possible wallets and databases.
5. Leave your new, clean wallet connected to that node and do the importprivkey thing with each of your keys you kept in that txt file. "importprivkey <privkey>" in debug console.
6. Let the wallet run that way  (connected to ubxidutptf2sslhq.onion:24112) until most of your acquired coinage is used (simply wait a few mins). After you mined a few blocks close your wallet and start it again (without "-connect=....")

Please do every step as written. Especially the restarting without "-connect" at the end

Now check again:

getblockhash 12460

4df338563eb017db366be9568e9595f8e2b18580fe0d361db4022ad8c6add694


Problems? Tell me.
(brb - 1 to 2 hours)

if you have more than one staking wallet: do one first - wait a few mins - do the 2nd. this way you decrease the risk of creating a "private fork".

Did you download the newest bootstrap?  If you're connecting to the lxtra, it's probably the old one.  Also, the block explorer is this node: ubxidutptf2sslhq.onion:24112 so it's best to use that one.  Follow the directions exactly as wurstgelee outlines above.  Dump the private key for your TUtMhWTrbRHx6o5Wt7Fj115AGzBrnAScXz address and sync with no wallet, only the newest bootstrap.  It should be a fairly painless sync.

[wurstgelee]

I love the idea of having a game. Although i think you're thinking maybe way to complicated for a first step.

How about a simple, modified faucet (with gaming factor)?:

- 3 instead of 24 cards, 1 Jackpot card with fixed amount, maybe 1 TRI.
- maybe 1 Pick per IP and 1 (3?, 5?, 8?) hour
- if user picks right cards, he gets send TRI to the address he entered in some formfield prior to picking a card
- no account system, user only enters TRI address (we love anonymity!)

I like the simplified idea as a kind of faucet.

Since money (TRI) is involved, it would have to be secure - "provably fair", so the right pick has to be known to the server in advance.

Yes, I am aware of this.
This is what I mean with "Cheat-Proof". I will try to integrate a system, where the correctness can be prooven without disclosing the right pick.

What do you think, could you create such a thing and what would you need? (A server with a running wallet would be no problem. Also a database. What else?)
PS: Thats Javascript I suppose/hope?

I can create such a faucet with a gambling factor. What I need is a running wallet, a database, server-side scripts and client-side scripts (Yes, Javascript).
So everything what is needed for a normal WebApp (except the wallet). But I already worked with the wallet over RPC, so this should not be a problem.
I will develop this faucet first on my playground and later some Beta-Tester are needed. How and where this faucet is hosted can later be clarified.

I would happily hook you up with everything you need. I could offer you a mysql-db and a tomcat or a jetty (if thats enough) reverse proxied by an apache2. And probably anything else you need.

[wurstgelee]

I did it quick and dirty. I'm not really happy with it but ...here it is:

http://info.triangles.technology

I thought it might be a good thing to provide at least the wallet downloads and the bootstrap at a centralized place.
So it's nothing more than a placeholder for the final site.

[StephenJH]

snazzy ^

[wurstgelee]

.ninja {color:000; visibility:hidden;}

Wurst want to set up a community donation address to fund the faucets and games?[or delegate]

I'm on some mediterranean island for 5 days starting tomorrow.

But even without that I would gladly share responsibilities and work. So yes, if you like to to something, do it.

[richiela]

Guys, i've been trying to get synced all the way.  This usually happens after block 13000

ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake fff23827e8b0625b9feae1b2ddadc06d5efc4f8d904dfb5327164791aeecb0ff, hashProof=dbc40f0051f4f4a786b76e1de750dcd426e1b66571d5ffe9ef34541687583d85
WARNING: ProcessBlock(): check proof-of-stake failed for block 7c77066ed3d686ae6ed3fe42d41ca00029c125449c0ab3f9f178d48bb6a686ff
received block fc984ec25ff21f218996
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 3e840aa35046817ca3d2b37c192abd25c2276c6a1d2773faa11ae7d0817f7de2, hashProof=8ba89d084bd539ede2d1ebab7f3a4f549af2644271b40f2ada355f7f97679a61
WARNING: ProcessBlock(): check proof-of-stake failed for block fc984ec25ff21f218996b160e05305881e57c5fd0321698a97ba61cd4e4cd31b


Any suggestions?  tried the bootstrap.. tried the connect... never had this many problems trying to sync

Thanks
richie@bittrex

[richiela]

Guys, i've been trying to get synced all the way.  This usually happens after block 13000

Any suggestions?  tried the bootstrap.. tried the connect... never had this many problems trying to sync

Thanks
richie@bittrex

Updated Log - this is with the bootstrap and connect

ProcessBlock: ACCEPTED
received block e34aba6767205a9329eb
SetBestChain: new best=e34aba6767205a9329ebe14477b131586731d598704e6ddb1d26d9aa2c4df91f  height=12999  trust=12252548499135  date=09/01/14 02:27:14
Stake checkpoint: cfd8aa87
ProcessBlock: ACCEPTED
received block 439af16a54133cc2a826
SetBestChain: new best=439af16a54133cc2a826905e42f8bbc55ae2f51ad3a459eb8192a35c2134d1e7  height=13000  trust=12252551597590  date=09/01/14 02:27:35
Stake checkpoint: 6e0d4e98
ProcessBlock: ACCEPTED
received block ef56e35c70c8c19bf04c
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 185902636f2af2be3b4b2f3e5ab12bf5695a10844e0b6887849f6683c80bf6be, hashProof=96a7c4610a827ea197c8dbc006ec5075f989a05a69992afa934049fd910d97d1
WARNING: ProcessBlock(): check proof-of-stake failed for block ef56e35c70c8c19bf04c2a1231305ded1a418e01a044f5ce2bcdcf302ef20199
received block 303958c1c53893142e1a
ProcessBlock: ORPHAN BLOCK, prev=ef56e35c70c8c19bf04c
received block 3e486e5d501c3cf8177c
ProcessBlock: ORPHAN BLOCK, prev=303958c1c53893142e1a
received block 26a82d59362acb3a335b
ProcessBlock: ORPHAN BLOCK, prev=3e486e5d501c3cf8177c
received block a3dde4cc0774068705a3
ProcessBlock: ORPHAN BLOCK, prev=26a82d59362acb3a335b
received block 6e79eac97bfc35cbe381
ProcessBlock: ORPHAN BLOCK, prev=a3dde4cc0774068705a3
received block bcfab098560087faca12
ProcessBlock: ORPHAN BLOCK, prev=6e79eac97bfc35cbe381
received block 6d2b585deb06fd70491a
ProcessBlock: ORPHAN BLOCK, prev=bcfab098560087faca12
received block 4cdc954b86aeb44f07b0
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 5935d448e7e89f68468045a7d6c3f8afdba472a2ef547f0b504f397d65f13612, hashProof=99b86c096dba2a8e29a9fe9fcfc5750c50795072fa77f74c51d8b391a996a1f9
WARNING: ProcessBlock(): check proof-of-stake failed for block 4cdc954b86aeb44f07b00d4004141e0060d9473336edce87722150d70009455e
received block 1d155ec2a899f325fe35
ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 431c97002c166dcad909d9830082e1869b3664df801156b6882d45d532a2c4d5, hashProof=93ba1498bc719fb3804e996667b1c6548fdc4a3e9b9f1d7a5f96471161df9403

[wurstgelee]

I checked my chains with -checkblocks=0, came up clean with 17509 blocks. I updated the bootstrap @ http://info.triangles.technology/#download to those 17509 blocks.

Could you try that? Also maybe start the wallet once with "-connect=ubxidutptf2sslhq.onion:24112" (24/7 block explorer node) until you are sync. Then restart without.

Please let me know if you still face problems.

//wurstgelee

edit: obviously still guys on that broken fork... :/

[wurstgelee]

i guess i found the issue. the block explorer will be unavailable for an hour or so - testing stuff.

[StephenJH]

Aren't you on an Island?! 

[wurstgelee]

Aren't you on an Island?! 

Not yet. Plane in ~ 4 hours.

[StephenJH]

I notice the explorer is up... should I turn my wallets on?

[wurstgelee]

I notice the explorer is up... should I turn my wallets on?

Yep - but please connect with -connect="ubxidutptf2sslhq.onion:24112" until youre synced first. shouldnt be necessary - but wouldnt harm either.

Still examining things, brb with more infos.

[wurstgelee]

Ok, small update - I have to catch a plane!

There obviously is a problem with clients trying to fully sync from bootstrap.dat.

"-checkblocks=0" doesnt throw an error though - so you face no problems if u only check your own blockchain copy.

I narrowed it down to some changes 3angle made in the sources earlier. I will continue to further investigate this issue and fix it. Since I´m on holidays from now on, this might take a few days. In the worst case, this will happen next Tuesday - when I return.


This means:

- Do nothing if you have a running, synced wallet -  just let the minting roll.
- If you face any problems, make sure you`re synced to ubxidutptf2sslhq.onion:24112 (block explorer node)
- If you can't sync - don't put too much effort in this. It will be fixed, no coins will be lost.
- Do not panic.

PS: This issue was discovered when bittrex tried to sync their wallet. I verified it and can reproduce it.
PPS: I will most likely check in later that day.

[StephenJH]

Go have fun dood jeez! I'm pretty sure those here aren't the panic type. Whatever panic was going to happen already did.