[XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS

[atleticofa]

Price manipulation again

[profitofthegods]

I followed the instructions for Amazon EC2 and it seems to be running the node, but I can't access the wallet. Is the 'server ip' just the public ip listed under my instance - because that seems to be unreachable. Anybody know why?

[SyRenity]

Is the following command correct?  

docker run crypti/node sed -i 's/""/"PASSWORD"/g' /src/config.json

Edit:  Please post an example for the hypothetical passphrase XCRisDaBomb.

docker run crypti/node sed -i 's/""/"XCRisDaBomb"/g' /src/config.json

Seem to be fine:
http://take.ms/lZNI1

[SyRenity]

I followed the instructions for Amazon EC2 and it seems to be running the node, but I can't access the wallet. Is the 'server ip' just the public ip listed under my instance - because that seems to be unreachable. Anybody know why?

Have you tried adding the port 6040 (Crypti default port)?

Also, you might need to open the AWS firewall rules to allow access to this port.

[SyRenity]

when will downloadable wallet be available?

Downloadable is already available:
http://downloads.crypti.me/crypti-node/0.1.1/crypti-linux-0.1.1.zip

Docker is temporary disabled, will be restored soon.

[SyRenity]

SyRenity
I have installed node on amazon and digital. And both my nodes can't sync.

What could be wrong? I have something set up wrong? The first time I am dealing with these clouds.

Can you PM Boris (crypti) the logs? They should be in same or one above directory, together with the blockchain.db file.

[poornamelessme]

One has to be extra-dumb to dump on the market like this. Some patience would have made that person quite a bit richer.

More for me I guess!

2014-08-22 05:57:21   Buy   XCR/BTC   0.00002017 BTC   30,000.000000 XCR   0.6051 BTC
2014-08-22 05:57:21   Buy   XCR/BTC   0.00002101 BTC   30,000.000000 XCR   0.6303 BTC
2014-08-22 05:57:21   Buy   XCR/BTC   0.00002262 BTC   30,000.000000 XCR   0.6786 BTC
2014-08-22 05:30:47   Buy   XCR/BTC   0.00002379 BTC   30,000.000000 XCR   0.7137 BTC

I suppose some folks always buy on rumor and sell on news, even though it's sort of asinine to consider a coin's release 'news' to sell on.

[karmacoma24]

How many confirmations before my balance becomes confirmed?

[SyRenity]

I keep getting this...  sed: -e expression #1, char 10: unknown option to `s'   

Scramble the password (with http://4umi.com/web/javascript/scramble.php) and please and PM me the full command you are using with the scrambled password.

[Sparky_eMunie]

Code:

docker@boot2docker:~$ docker run -d -p 6040:6040 crypti/node
Unable to find image 'crypti/node' locally
Pulling repository crypti/node
2014/08/21 22:11:40 HTTP code: 404
docker@boot2docker:~$

[PilotofBTC]

any plans to publish the wallet as a node package?

[LetMeKnow]

One has to be extra-dumb to dump on the market like this. Some patience would have made that person quite a bit richer.

More for me I guess!

2014-08-22 05:57:21   Buy   XCR/BTC   0.00002017 BTC   30,000.000000 XCR   0.6051 BTC
2014-08-22 05:57:21   Buy   XCR/BTC   0.00002101 BTC   30,000.000000 XCR   0.6303 BTC
2014-08-22 05:57:21   Buy   XCR/BTC   0.00002262 BTC   30,000.000000 XCR   0.6786 BTC
2014-08-22 05:30:47   Buy   XCR/BTC   0.00002379 BTC   30,000.000000 XCR   0.7137 BTC

Jea, dont undestand how can someone sell for 2000.. hmm. maybe some bots.

Great buy actually!

[SyRenity]

Let's keep it simple...  I entered the exact one you posted and didn't get the error (same thing happens if I leave PASSWORD)...  but config.json still shows "".

Have you commited (as per the next step)?

[SyRenity]

2014/08/21 22:11:40 HTTP code: 404

Docker is temporary disabled, we just pushed an note to guide:
https://github.com/crypti/crypti-docs/blob/master/boot2docker.md

[SyRenity]

Hey! You have plans for bittrex or mintpal? I have more friends who want to invest but little frighened by bter  

We are working on the next integrations at the moment, and will announce them onwards.

[SyRenity]

any plans to publish the wallet as a node package?

Yes, we have such task in ToDo list, provided we solve the Windows libraries matter.

[lrgbit]

Hello,

I am getting this in my log when running a node

{"level":"error","message":"Payload hash invalid: 12315905898351867984","timestamp":"2014-08-21T22:17:23.521Z"}
{"level":"info","message":"Crypti stopped!","timestamp":"2014-08-21T22:17:23.521Z"}

Any ideas?

Cheers

[freeworm]

We owe Crypti investors and the dev team an apology.
We actually finished the integration with the dev team about 10 days ago.
After the NXT event happened, we focused all our energy on  a new security system which makes not only the cold wallet but also the hot wallet very safe.
In the past a few days, we have done a lot testing of Crypti wallet as an exchange with the dev team.
I have to say the Crypti team is great! I have had a happen time working with them.

Good luck to Crypti and all investors. We are doing our best to support it as an exchange!

Best,
Lin @ BTER

[profitofthegods]

I followed the instructions for Amazon EC2 and it seems to be running the node, but I can't access the wallet. Is the 'server ip' just the public ip listed under my instance - because that seems to be unreachable. Anybody know why?

Have you tried adding the port 6040 (Crypti default port)?

Also, you might need to open the AWS firewall rules to allow access to this port.

I did have the port, it must be the AWS firewall rules but looking at the AWS help section for security groups is like looking at anything written for programmers - its completely impenetrable to me. Does anybody know how to set up a security group on AWS that will let me access the wallet?

[prix]

I did have the port, it must be the AWS firewall rules but looking at the AWS help section for security groups is like looking at anything written for programmers - its completely impenetrable to me. Does anybody know how to set up a security group on AWS that will let me access the wallet?

Go to "EC2 Dashboard", select your instance, click on the security group in the last column of table.