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

[dzarmush]

Starik?  DO you read the other posts?  I already wrote that the foundation delegates, which were necessary to create in order to get the system running properly, will be down voted soon, so the public can have forging delegates.

His logic is out of regular people understanding. Right now he's in berserk posting mode and his reading mode is off.

[dzarmush]

Avast doesn't like node.exe, thinks there's an infection for some reason when I launch the client. Should I ignore it/re-install nodejs/other options?

[Litoshi]

Mal,

Great detective work.  

One interesting thing about that list of accounts........... seems that about half of the accounts have less than 1 XCR in them.  

I imaging these are abandoned accounts, who moved XCR to exchanges and were unsure of the transaction fees, so left a little change on the table.  

There are another 240 or so accounts with just 50.00000 XCR in them.  These are one time faucet visitors.  Many could also belong to the malcreant that was click slamming the faucet one weekend.  

[Litoshi]

Avast doesn't like node.exe, thinks there's an infection for some reason when I launch the client. Should I ignore it/re-install nodejs/other options?

node,exe is the Crypti client.  I got the same virus warnings, not because theer was a detection, but due to its being new software with few users.  Check the certificate under properties.  The XCR installer is signed.

[dzarmush]

Avast doesn't like node.exe, thinks there's an infection for some reason when I launch the client. Should I ignore it/re-install nodejs/other options?

https://i.imgur.com/6lXcFI1.png

node,exe is the Crypti client.  I got the same virus warnings, not because theer was a detection, but due to its being new software with few users.  Check the certificate under properties.  The XCR installer is signed.

Ok.

I thought there might be a problem with nodejs. Like Nxt client could be fine but Java on a computer is infected.

[Litoshi]

Avast doesn't like node.exe, thinks there's an infection for some reason when I launch the client. Should I ignore it/re-install nodejs/other options?

https://i.imgur.com/6lXcFI1.png

node,exe is the Crypti client.  I got the same virus warnings, not because theer was a detection, but due to its being new software with few users.  Check the certificate under properties.  The XCR installer is signed.

Ok.

I thought there might be a problem with nodejs. Like Nxt client could be fine but Java on a computer is infected.

node.js is used by other software besides Crypti.  It is possible that you picked up a virus from another program or web site.

[dzarmush]

node.js is used by other software besides Crypti.  It is possible that you picked up a virus from another program or web site.

Looks like Avast just doesn't like it's trying to connect to http://104.238.133.14:8080 which is, I assume, Crypti node? So I should be fine.

[starik69]

I am looking at my bandwidth, at myriads of useless empty blocks, and thinking that something is very very wrong.
My node almost always 10-20 minutes late and syncing and syncing.
A moment i see the last block >3000 and then blockchain rollbacks to 2700.
This strict 10s block is something wrong in means of global network.
Latencies kills this. Even in NXT there is 15s timeframe to forge a block.
Seems like the devs didnt learn their lessons from POT failure and making same mistakes.

[Litoshi]

node.js is used by other software besides Crypti.  It is possible that you picked up a virus from another program or web site.

Looks like Avast just doesn't like it's trying to connect to http://104.238.133.14:8080 which is, I assume, Crypti node? So I should be fine.

port 8080?  the client is on port 8040.   Try manual editing of the address.

Check the config.json.  make sure the port is listed as 8040

[dzarmush]

node.js is used by other software besides Crypti.  It is possible that you picked up a virus from another program or web site.

Looks like Avast just doesn't like it's trying to connect to http://104.238.133.14:8080 which is, I assume, Crypti node? So I should be fine.

port 8080?  the client is on port 8040.   Try manual editing of the address.

Check the config.json.  make sure the port is listed as 8040

I miss-typed, 8040 of course.

[MalReynolds]

........... seems that about half of the accounts have less than 1 XCR in them.  

465 accounts have 1 XCR or less out of a final 0.2.0 account total of 1160 or fewer.

From a detective standpoint, it would be interesting to monitor what new accounts are created in the future that receive funds from 983470101446368718C and 6746720336938643271C (Bter), 1064014217195323888C (Poloniex) and 17633453026976314980C (Cryptsy?).

[dzarmush]

My node almost always 10-20 minutes late and syncing and syncing.

Try to switch dial-up to something better  

[MalReynolds]

So what is the 0.2.0 fee to install a second payout passphrase?

Not that I intend to do so until a few days go by and the new blockchain is seen as stable...

[Litoshi]

........... seems that about half of the accounts have less than 1 XCR in them.  

465 accounts have 1 XCR or less out of a final 0.2.0 account total of 1160 or fewer.

From a detective standpoint, it would be interesting to monitor what new accounts are created in the future that receive funds from 983470101446368718C and 6746720336938643271C (Bter), 1064014217195323888C (Poloniex) and 17633453026976314980C (Cryptsy?).

Yes would be interesting.  Sounds like you found yourself a project.  Beats traveling around the galaxy, getting into a gun fight twice every episode?

[MalReynolds]

XCR Frozen at Dev request.

Posted by GeezUp at 2015-04-09 17:17:27 in Polo notice box.

https://poloniex.com/exchange#btc_xcr

[Wulfcastle]

The release of Chronos

Finally we can announce the release of v0.2.0 alias Chronos. Besides various bug fixes and speed improvements, we introduce our new consensus mechanism with it. It's called DPoS (Delegates Proof-of-Stake) and it is suited the best for our later releases (Dapp Store). At our blog post An introduction to DPoS you can read more about DPoS.


Our latest blog post shows everything you need to know about this release. If you encounter any issues, then please post them to our Helpdesk. We will happily help you out with them. If you want to become a delegate you can also ask in the Helpdesk.


Windows: http://downloads.crypti.me/crypti-node/0.2.x/crypti-windows-0.2.0.exe

Mac OS: http://downloads.crypti.me/crypti-node/0.2.x/macos-0.2.0.zip

Linux: http://downloads.crypti.me/crypti-node/0.2.x/0.2.0.zip


Thank you all that you waited the whole day. We were very busy all the time and it was quite complicated for us all, as we are living throughout the whole world. Some of us are awake since 24h, but we think that it was all worth it!


Edit:

A few more things about the Forging and Delegate features.
- It costs you 10,000 XCR to be a delegate
- You need enough votes to get into the top 101 to actually forge and earn XCR that way
- It takes a maximum of 17 minutes (one full round 101*10sec) to see your votes

push

Bumping this to the new page.

[Wulfcastle]

Okay as most of you may know, CryptiChat : http://www.cryptichat.me/, has been in BETA for about 2 weeks now, and after quite a bit of testing and use, I'm ready for it to officially launch.

So coinciding with the launch of 0.2.0 (Chronos), as of today Cryptichat, is officially launched!


XCR Giveaway

I'll be hosting a 5K XCR Giveaway tomorrow night at 9PM UTC, whoever wants to receive some of the 5K XCR all you'll need to do is join the chat to receive your free XCR. You'll see the rest of the info when you connect

[karmacoma24]

CryptiKit Update - Simple & easy Crypti node deployment and management.

Hello Everyone!

Coinciding with the brand spanking Chronos (v0.2.0) Crypti release. Today, I am very happy to bring you the latest update to CryptiKit!

Featuring full support for running multiple delegates on individual nodes, and an improved withdrawal system.

Please download here: https://github.com/karmacoma/cryptikit/releases/tag/v2.0.0

For further information about CryptiKit and what it can do, please read here:
- https://github.com/karmacoma/cryptikit/blob/v2.0.0/README.md

For the complete changelog, please read here:
- https://github.com/karmacoma/cryptikit/blob/v2.0.0/Changelog.md


Release Highlights

Delegates

• Adding delegate status information to check_nodes task
• Added support for running multiple delegates on individual nodes

For more information, please read:

• https://github.com/karmacoma/cryptikit/blob/v2.0.0/README.md#multiple-delegates
• https://github.com/karmacoma/cryptikit/blob/v2.0.0/README.md#checking-nodes

Example - Multiple Delegates



Withdrawals

• Renamed withdraw_surplus task to withdraw_balances
• Now allows users to withdraw specific balance
• Improved accuracy of network fee deduction
• User now presented with a list of accounts to withdraw from
• Recipient address is now specified using 'recipient' environment variable
• Improved error and log messages

For more information, please read:

• https://github.com/karmacoma/cryptikit/blob/v2.0.0/README.md#withdrawals

Example - Withdrawal

[jari76]

CryptiKit Update - Simple & easy Crypti node deployment and management.

Hello Everyone!

Coinciding with the brand spanking Chronos (v0.2.0) Crypti release. Today, I am very happy to bring you the latest update to CryptiKit!

Featuring full support for running multiple delegates on individual nodes, and an improved withdrawal system.

Please download here: https://github.com/karmacoma/cryptikit/releases/tag/v2.0.0

For further information about CryptiKit and what it can do, please read here:
- https://github.com/karmacoma/cryptikit/blob/v2.0.0/README.md

For the complete changelog, please read here:
- https://github.com/karmacoma/cryptikit/blob/v2.0.0/Changelog.md

Really awesome update karma


By the way, i have a question about the 10k fee for making a delegate, why is it there? at the moment it is just s transfer of 10k XCR to the dev nodes.
will this (101*10k = 1 million Crypti)  be used for the Delegate-reward program later on?

it seems like a fair system for making new delegate's, exept for the case it is now, where all the dev node's paid 0 XCR, and get the 10k from the community registering delegate's.

[starik69]

Oh, deleted blockchain, restarted client - now can not sync at all!
It is going circles - 3614 - 3707 - 3614 when there are 3876 the last block.
Why it can not sync?