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

[GreXX]

A Few Notes

So I have noticed many asking about the orphan like behavior and also the fork processing.

In the blog post, I mentioned it down in the notes, but it was kind of hidden. Here is a copy paste with relevant piece highlighted.

In the new system, you still need a client with your passphrase loaded and 1000 XCR to forge. Your client will try to win each block and may initially display that it has won. The network will then come to a consensus, announce the correct forger to nodes, and have the winner updated in your ledger. This means it may look like you won a block, however once the the block confirmed, it will update the winning node. This is also a normal behavior.

Basically what you are seeing is when the new block starts, your node trying to forge the block and saying it has won until it is told otherwise. You are just seeing the network update your node who the real winner is, and then logging it in the ledger.

Keep in mind this is an ever evolving temporary solution that may even turn into a permanent solution with enough tweaks to get the algorithm where we want it and clean it up a bit.

Also remember that we are doing a 1 min block time and the only transactions really occurring at the moment are transfers between users, exchanges, and passphrase fees. So we will still see a good number of zero fee blocks. The idea here is for everyone to see the potential of the system as we continue to build out and gain support. The more we build, the bigger we get, the more you will make for forging and the more full the blocks will become.

On the bright side, it looks like even with all of you coming online, we are all staying on the same fork (no more forking issues) and most here are getting it installed with little to no problems.

If you are still experiencing problems getting installed, please let us know! We will try to work through it with you.

Also, an install video is a great idea. As soon as Eric is available today I will talk to him about doing one for each version and see if we can get them posted to youtube.

As always, stick with us, we will keep you updated. We are happy to see you all still here and appreciate your support!

[MadGhost]

A Few Notes

So I have noticed many asking about the orphan like behavior and also the fork processing.

In the blog post, I mentioned it down in the notes, but it was kind of hidden. Here is a copy paste with relevant piece highlighted.

In the new system, you still need a client with your passphrase loaded and 1000 XCR to forge. Your client will try to win each block and may initially display that it has won. The network will then come to a consensus, announce the correct forger to nodes, and have the winner updated in your ledger. This means it may look like you won a block, however once the the block confirmed, it will update the winning node. This is also a normal behavior.

Basically what you are seeing is when the new block starts, your node trying to forge the block and saying it has won until it is told otherwise. You are just seeing the network update your node who the real winner is, and then logging it in the ledger.

Keep in mind this is an ever evolving temporary solution that may even turn into a permanent solution with enough tweaks to get the algorithm where we want it and clean it up a bit.

Also remember that we are doing a 1 min block time and the only transactions really occurring at the moment are transfers between users, exchanges, and passphrase fees. So we will still see a good number of zero fee blocks. The idea here is for everyone to see the potential of the system as we continue to build out and gain support. The more we build, the bigger we get, the more you will make for forging and the more full the blocks will become.

On the bright side, it looks like even with all of you coming online, we are all staying on the same fork (no more forking issues) and most here are getting it installed with little to no problems.

If you are still experiencing problems getting installed, please let us know! We will try to work through it with you.

Also, an install video is a great idea. As soon as Eric is available today I will talk to him about doing one for each version and see if we can get them posted to youtube.

As always, stick with us, we will keep you updated. We are happy to see you all still here and appreciate your support!

[matrix961]

A Few Notes

So I have noticed many asking about the orphan like behavior and also the fork processing.

In the blog post, I mentioned it down in the notes, but it was kind of hidden. Here is a copy paste with relevant piece highlighted.

In the new system, you still need a client with your passphrase loaded and 1000 XCR to forge. Your client will try to win each block and may initially display that it has won. The network will then come to a consensus, announce the correct forger to nodes, and have the winner updated in your ledger. This means it may look like you won a block, however once the the block confirmed, it will update the winning node. This is also a normal behavior.

Basically what you are seeing is when the new block starts, your node trying to forge the block and saying it has won until it is told otherwise. You are just seeing the network update your node who the real winner is, and then logging it in the ledger.

Keep in mind this is an ever evolving temporary solution that may even turn into a permanent solution with enough tweaks to get the algorithm where we want it and clean it up a bit.

Also remember that we are doing a 1 min block time and the only transactions really occurring at the moment are transfers between users, exchanges, and passphrase fees. So we will still see a good number of zero fee blocks. The idea here is for everyone to see the potential of the system as we continue to build out and gain support. The more we build, the bigger we get, the more you will make for forging and the more full the blocks will become.

On the bright side, it looks like even with all of you coming online, we are all staying on the same fork (no more forking issues) and most here are getting it installed with little to no problems.

If you are still experiencing problems getting installed, please let us know! We will try to work through it with you.

Also, an install video is a great idea. As soon as Eric is available today I will talk to him about doing one for each version and see if we can get them posted to youtube.

As always, stick with us, we will keep you updated. We are happy to see you all still here and appreciate your support!

Doh I missed that myself in the notes. Thanks for the explanation. With that said I definitely agree it's working well. im not seeing any other issues at this time. All of my nodes are at least 2gb servers so no issue with memory. It seems from some posts we have seen an increase in memory use. Will some more memory optimization be possible for those running with less memory?

You guys are doing a great job.

[shadowduck]

I confirm Linux client cannot get sync  
What a shame

+1
You guys do not want to listen to me, you have not solved the problem with memory
5000 Bitcoins, Litoshi for you all is well. When in fact the problem is not solved
If the memory problem is not resolved, the project can be considered a failure

All is well. All you do is bash Crypti and hail Node in all your posts.

I obviously don't share the same values as you do (bashing other coins thinking my coin is gonna become better because of that)
I rather contribute to what I believe to be superior technology to help it grow instead of trolling other threads.

I think that's why people don't listen to you

I support Crypti and have more than 200 000 coins, but for some reason you do not want to solve the fundamental problem. It's important now

For me, two problems:
1. It's rediculous that sync from network does not work, I must download the database separately
2. The memory consumption issue is not acceptable. You can't blame node-webkit, because for me it's run in a headless linux server, no node-webket is involved.
    and we can see that the memory consumption grows along with block loading. So the only reason is the horrible memory manament of crypti.

[SyRenity]

For me, two problems:
1. It's rediculous that sync from network does not work, I must download the database separately
2. The memory consumption issue is not acceptable. You can't blame node-webkit, because for me it's run in a headless linux server, no node-webket is involved.
    and we can see that the memory consumption grows along with block loading. So the only reason is the horrible memory manament of crypti.

1) The snapshot downloading is only done to speed-up the synchronization.
You can erase the file blockchain.db from your directory and restart Crypti Wallet, and it will retrieve the full blockchain from the other nodes from scratch.

It's quite similar to how today BTC blockchain is being distributed via torrents.


2) We are aware of this issue and will improve the RAM usage it in the next versions.

[Litoshi]

For me, two problems:
1. It's rediculous that sync from network does not work, I must download the database separately
2. The memory consumption issue is not acceptable. You can't blame node-webkit, because for me it's run in a headless linux server, no node-webket is involved.
    and we can see that the memory consumption grows along with block loading. So the only reason is the horrible memory manament of crypti.

When you restart the wallet/node it does not download the blockchain from the network again.  It first syncs its existing blockchain.db file (located in C:\CryptiWallet) with the network, and then downloads any blocks added since your last sync. 

I know it APPEARS as if it is downloading all over again....... I pointed this out in the testing we did prior to release.  It and a few other things are on the table to be changed.

[shadowduck]

For me, two problems:
1. It's rediculous that sync from network does not work, I must download the database separately
2. The memory consumption issue is not acceptable. You can't blame node-webkit, because for me it's run in a headless linux server, no node-webket is involved.
    and we can see that the memory consumption grows along with block loading. So the only reason is the horrible memory manament of crypti.

1) The snapshot downloading is only done to speed-up the synchronization.
You can erase the file blockchain.db from your directory and restart Crypti Wallet, and it will retrieve the full blockchain from the other nodes from scratch.

It's quite similar to how today BTC blockchain is being distributed via torrents.


2) We are aware of this issue and will improve the RAM usage it in the next versions.

For #1, I am not the only one met the scenario as you can see from the previous posts.

I DID remove the blockchain.db before I try to start the node again, but every time it stuck at the same block.
For me and the other one who met the issue, snapshot downloading is the only solution instead of just an approach to accelerating the sync process.

[informer]

I'm still trying to get a Linux node to work. But I'll be damn if I didn't get a windows wallet web-kit (w3K) installed and within 10 minutes forged 100 XCR!



btw- Its on an AWS t2.micro Windows 2012 R2 standard

~informer

[5000Bitcoins]

I posted https://bitcointalk.org/index.php?topic=821046.0

For some broader discussion than just limited here, invite forgers, maybe some brainstorming and new ideas.

(not a good writer I know) 

[SyRenity]

For #1, I am not the only one met the scenario as you can see from the previous posts.

I DID remove the blockchain.db before I try to start the node again, but every time it stuck at the same block.
For me the other one met the issue, snapshot downloading is the only solution instead of just an approach to accelerating the sync process.

Thanks for the report, looking into this.

[karmacoma24]

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

Hello Everyone! This release coincides with the release of Crypti Node 0.1.7. It contains some important bug fixes, improvements to the installation process and a general refactoring of the code base.

Please download here: https://github.com/karmacoma/cryptikit/releases/tag/v1.5.1

If you don't know about CryptiKit and what it can do already, please read here:
- https://github.com/karmacoma/cryptikit/blob/v1.5.1/README.md

Changelog

Updates

• Updated crypti node to latest version: 0.1.7
• Updated blockchain download url

Bug Fixes

• Fixed targeting of servers when a range is provided
• Fixed checking of remote dependencies when crypti node has not been installed yet
• When running the automated update script:
  
  • Latest stable release of rvm is installed
  • Gems are updated and old versions removed
  • CrypiKit gemset is recreated if missing

Auto-completion

• Moved bash auto-completion script to bin/completer.rb

On existing installations, please run the following command to re-enable bash auto-completion:

Code:

ruby bin/completer.rb --re-enable

Cheers, Karmacoma24.

[5000Bitcoins]

Now that we know how SuperNet is and it's impact, what do we think of it? I know we dismissed the idea in the past but now that we've seen what it is it is worth a second thought.
Crypti is only as useful as it is used, it is a currency made for using - without usage, it fills no functions. Holders, spenders, forgers.
Joining supernet in Crypti's case in my opinion isn't "hoping for a quick raise, or buck, then it will return to normal" but more so an increased value in the network which thrives on movement.

In my opinion it could help XCR. Volume wise, transactionwise, exposure & new forgers, arbitrage incentive to move coins etc.
Just trying to brainstorm how we can attract and award forgers while waiting for new business so people aren't forging empty transactions.
We need to make people move their coins, buy and sell to make a healthy network.


More than less, in my humble opinion.

[imd1]

I'm still trying to get a Linux node to work. But I'll be damn if I didn't get a windows wallet web-kit (w3K) installed and within 10 minutes forged 100 XCR!



btw- Its on an AWS t2.micro Windows 2012 R2 standard

~informer

Can you please explain more on how you're doing this ? I would like to do the same.

My wallet has forging enabled for almost 2 hours now but nothing forged yet. 

[meccoin4me]

all this is new for me , have to read a lot of info but all this sounds interesting .

before i am going to read what is the big difference between mining and forging??

i am doing it already btw , lol

[5000Bitcoins]

all this is new for me , have to read a lot of info but all this sounds interesting .

before i am going to read what is the big difference between mining and forging??

i am doing it already btw , lol

Not sure of the technicalities someone else in here probably more suited to talk about that but I do know that that mining costs serious amounts of $ in terms of hardware, not guaranteed profits and will take a while to recoup your investment, and also unable to compete with others if you lack capital.

Forging in XCR means everybody is equal, it costs about 1000 XCR or about $4.95 per guy (doesnt even really cost them that just requires you have in wallet, they can always sell if they don't wanna forge anymore)


I wonder more about questions such as which network is more safer when we reach X amount of forgers etc how much safer each forgers makes network, thing I know is more forgers the safer healthier network.

I want to make more forgers, for that to happend network needs to have transactions etc, so people earn so in start it might not be as profitable if you don't hit large transactions tho.
That being said, the little forgers it is now it is higher chance of happening, later on when there is more forgers, more fees will be split inbetween so evens out I think.
And with ppl like Litoshi hitting faucets every day, I am sure there are many who don't mind, but in time the network of forgers will see profit.

Bottomline is both are just different ways of keeping the network secure, with forging being in my opinion the superior because more people can feel they contribute, even the lazy also without spending $7000 on rigs.

[Litoshi]

Now that we know how SuperNet is and it's impact, what do we think of it? I know we dismissed the idea in the past but now that we've seen what it is it is worth a second thought.
Crypti is only as useful as it is used, it is a currency made for using - without usage, it fills no functions. Holders, spenders, forgers.
Joining supernet in Crypti's case in my opinion isn't "hoping for a quick raise, or buck, then it will return to normal" but more so an increased value in the network which thrives on movement.

In my opinion it could help XCR. Volume wise, transactionwise, exposure & new forgers, arbitrage incentive to move coins etc.
Just trying to brainstorm how we can attract and award forgers while waiting for new business so people aren't forging empty transactions.
We need to make people move their coins, buy and sell to make a healthy network.


More than less, in my humble opinion.

Hey 5000.... could you enlighten me on the latest on SuperNet?  I and the others have been so involved with this coin that we have not paid any attention to the competition.  Either here or in your new BTT thread. TIA

[Litoshi]

all this is new for me , have to read a lot of info but all this sounds interesting .

before i am going to read what is the big difference between mining and forging??

i am doing it already btw , lol

Mining is accomplished by a computer using its CPU, or GPU cards, or an ASIC unit to receive a block hash which is then run through all possible combinations of an encryption algorithm to get a specified net value, usually X number of zeros front/rear or both.  With the present state of the art and difficulty in most coins, mining is no longer profitable as it consumes more electricity than the value of the mined coins.

Miners also verify transactions that have occurred on the network and earn a small amount of coins for that effort.  A minumum number of transactions and therefore miners are needed to verify a transaction, usually 6 to 60, depending upon the coin.

Forging is using your computer CPU to verify transactions that occur in the network.  This is how coins that cannot be mined have their transactions verified, and keep the network open and running.  The computer that forges (verifies) the block earns a portion of the transaction fee. 

[5000Bitcoins]

Now that we know how SuperNet is and it's impact, what do we think of it? I know we dismissed the idea in the past but now that we've seen what it is it is worth a second thought.
Crypti is only as useful as it is used, it is a currency made for using - without usage, it fills no functions. Holders, spenders, forgers.
Joining supernet in Crypti's case in my opinion isn't "hoping for a quick raise, or buck, then it will return to normal" but more so an increased value in the network which thrives on movement.

In my opinion it could help XCR. Volume wise, transactionwise, exposure & new forgers, arbitrage incentive to move coins etc.
Just trying to brainstorm how we can attract and award forgers while waiting for new business so people aren't forging empty transactions.
We need to make people move their coins, buy and sell to make a healthy network.


More than less, in my humble opinion.

Hey 5000.... could you enlighten me on the latest on SuperNet?  I and the others have been so involved with this coin that we have not paid any attention to the competition.  Either here or in your new BTT thread. TIA

I took out my contact lenses to rest my eyes, I'll do a writeup tomorrow and contact jl777 about it to get the full picture

[informer]

I'm still trying to get a Linux node to work. But I'll be damn if I didn't get a windows wallet web-kit (w3K) installed and within 10 minutes forged 100 XCR!



btw- Its on an AWS t2.micro Windows 2012 R2 standard

~informer

Can you please explain more on how you're doing this ? I would like to do the same.

My wallet has forging enabled for almost 2 hours now but nothing forged yet. 

It was truly luck of the draw. I've read somewhere on here that it goes to the forge that's been up longest. But that can't be true 'cause they would then all go to the main servers on not the forgers out here like you and I. If you have a wallet forging already on say a home PC you may want to consider launching a virtual machine in a cloud service somewhere like Amazon Web Services or digital ocean (there's a lot out there just goolge free cloud servers). They have very high availability and a lot of the micro servers out there are actually free of charge. There are some guides out there on how to get started with those:

https://github.com/crypti/crypti-docs

http://aws.amazon.com/
Here instead of creating an ubuntu server just choose Windows 2012 R2 Standard instead. Then connect from within your AWS console.

~btw I haven't forged any additional XCR since that first 100 today.

~informer

[informer]

OK, need some help guys. Using the official crypti guide:

https://github.com/crypti/crypti-docs/blob/master/install.md

Which you guys know I've installed successfully many times. On my linux AWS t2.micro, i've re-installed and ran it many different way and still get the same outcome. I've tried restarting app.js, i've tried deleting logs.log and restarting. deleting blockchain.db, deleting both blockchain and logs. Every time it results in the same thing. When I go to the web wallet I see this screen over and over. The only thing that changes is the block number its on and when it gets to the last one it starts over.



I once saw the login screen briefly but then it went back to the loading screen. Any ideas?

Can someone please update the blockchain.db.zip here?

http://downloads.crypti.me/blockchains/blockchain.db.zip

~informer