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.
Topic: [XCR] Crypti | Dapps | Sidechains | Dapp Store | OPEN SOURCE | 100% own code | DPoS - page 223. (Read 804701 times)
October 12, 2014, 12:07:37 PM
October 12, 2014, 11:55:00 AM
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
Bug Fixes
Auto-completion
On existing installations, please run the following command to re-enable bash auto-completion:
Cheers, Karmacoma24.
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. October 12, 2014, 10:51:03 AM
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.
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.
October 12, 2014, 10:45:48 AM
I posted https://bitcointalksearch.org/topic/xcr-lets-talk-crypti-and-other-nodejs-projects-821046
For some broader discussion than just limited here, invite forgers, maybe some brainstorming and new ideas.
(not a good writer I know)
For some broader discussion than just limited here, invite forgers, maybe some brainstorming and new ideas.
(not a good writer I know)
October 12, 2014, 10:42:13 AM
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
btw- Its on an AWS t2.micro Windows 2012 R2 standard
~informer
October 12, 2014, 10:24:11 AM
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. 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.
October 12, 2014, 10:00:38 AM
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.
October 12, 2014, 09:59:04 AM
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. 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.
October 12, 2014, 09:43:05 AM
I confirm Linux client cannot get sync 
What a shame
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.
October 12, 2014, 09:41:47 AM
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?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!
You guys are doing a great job.
October 12, 2014, 09:32:29 AM
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!
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!
October 12, 2014, 09:23:16 AM
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!
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!
October 12, 2014, 09:12:32 AM
I confirm Linux client cannot get sync
What a shame
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
So you quote the biggest troll here to make a point?
On Windows, the Crypti Wallet is using ~700MB of RAM. The only reason it is using so much is because the application itself is running through node-webkit, which is a memory hog itself.
For node-webkit 700 Mb is a lot
Your competitor NODE also uses node-webkit, you know how much memory it uses. Not more than 70 mb.
Your more than welcome to try to build a better version. Good Luck!
October 12, 2014, 08:43:37 AM
20 BTC sell wall on 1000 sat, whats wrong with Crypti.. such big amount of IPO, what do devs with the BTc?
don't worry)) everything will be cool) speculators...
Those 20BTC sell wall and many others on Bter before that, are all FAKE! This is just a game for big holders of Crypti are playing so people dump their holdings for small price.
So dont get bothered by this.
As the financial advisor and bookeeper for Crypti, I can assure you that the IPO BTC is safely stored in two exchanges. No funds get spent or withdrawn without 5 people agreeing on the payment, and 3 signing off on it with multisigs and 2FA.
Crypti does not use their funds to manipulate the coin price.
Absolutely!
I didnt mean that Crypti devs are playing with price though.
Yes, I know..... it was the original post by twistelaar
October 12, 2014, 08:42:15 AM
20 BTC sell wall on 1000 sat, whats wrong with Crypti.. such big amount of IPO, what do devs with the BTc?
don't worry)) everything will be cool) speculators...
Those 20BTC sell wall and many others on Bter before that, are all FAKE! This is just a game for big holders of Crypti are playing so people dump their holdings for small price.
So dont get bothered by this.
As the financial advisor and bookeeper for Crypti, I can assure you that the IPO BTC is safely stored in two exchanges. No funds get spent or withdrawn without 5 people agreeing on the payment, and 3 signing off on it with multisigs and 2FA.
Crypti does not use their funds to manipulate the coin price.
Absolutely!
I didnt mean that Crypti devs are playing with price though.
October 12, 2014, 08:36:26 AM
20 BTC sell wall on 1000 sat, whats wrong with Crypti.. such big amount of IPO, what do devs with the BTc?
don't worry)) everything will be cool) speculators...
Those 20BTC sell wall and many others on Bter before that, are all FAKE! This is just a game for big holders of Crypti are playing so people dump their holdings for small price.
So dont get bothered by this.
As the financial advisor and bookeeper for Crypti, I can assure you that the IPO BTC is safely stored in two exchanges. No funds get spent or withdrawn without 5 people agreeing on the payment, and 3 signing off on it with multisigs and 2FA.
Crypti does not use their funds to manipulate the coin price.
October 12, 2014, 08:25:03 AM
20 BTC sell wall on 1000 sat, whats wrong with Crypti.. such big amount of IPO, what do devs with the BTc?
don't worry)) everything will be cool) speculators...
Those 20BTC sell wall and many others on Bter before that, are all FAKE! This is just a game for big holders of Crypti are playing so people dump their holdings for small price.
So dont get bothered by this.
October 12, 2014, 08:24:46 AM
I confirm Linux client cannot get sync
What a shame
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
It appers you are an expert!
I think it would be much more usefull to give solutions rather than criticize regarding your expertise. Especially if you in a strange way somehow support Crypti.
A little research on his other BTT posts reveals this:
25 Other / Announcements (Altcoins) / Re: [AИN] NODE - Official Discussion Thread! Distributing the coins! on: 12-08-2014, 07:03:24
Quote from: HunterMinerCrafter on 12-08-2014, 06:19:44
Quote from: Coinr88 on 12-08-2014, 03:39:04
Quote from: michaelb87 on 12-08-2014, 03:27:53
For anyone interested, I'm selling my stake for 0.5 BTC because I need some money...
Node Buy / Sell Thread
How can you buy/sell a coin on a stalled chain? Caveat emptor!
You just say how bad the situation is,
I myself am a developer on node.js and watching the project and see that the work is done big. You only blame the developers.
You want that first version was perfect, even cripty developed on node.js faced with problems https://bitcointalk.org/index.php?topic=654463.3760
Please be patient
ReplyReply Reply with quoteQuote Notify of repliesNotify
October 12, 2014, 08:18:01 AM
I confirm Linux client cannot get sync
What a shame
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
It appers you are an expert!
I think it would be much more usefull to give solutions rather than criticize regarding your expertise. Especially if you in a strange way somehow support Crypti.
October 12, 2014, 08:05:29 AM
I am now forging.
Took me 1 minute to set up. Ridicuously easy, why hasn't this become 100x more popular than mining stuff?
I spend nothing, I do nothing yet I earn and contribute. Will let you in how goes in terms of return on investment after I let it run for a while. Very smooth sailing.
Took me 1 minute to set up. Ridicuously easy, why hasn't this become 100x more popular than mining stuff?
I spend nothing, I do nothing yet I earn and contribute. Will let you in how goes in terms of return on investment after I let it run for a while. Very smooth sailing.
Because of the TEMPORARY random algo that replaces the Proof of TIme Algo, you will see almost every block show up on your forging screen as a forge. It is only a possible forge. Every node online gets this possible forge, then one is chosen at random for the actual forge.
You can also see this in the blockchain tab. Your wallet number will show as the generator for the top block, then be replaced by the lucky wallet.
Again, this is only a temporary measure until the PoT algo is bug free
Litoshi, as far as you know, will the upcoming fix for the PoT algo (not the current temporary solution), retain the consistent block times that the current solution has brought about?
I am not a coder. My position here is community relations, financial advisor, and now bookeeper was added to my job.
Boris (Crypti) is the main coder.
As far as I know, the Proof of Time algo and the custom blockchains are the two most important features for this coins immediate future. Boris has had little sleep for the past week, putting in 20 hour days. Once he has caught up on his sleep debt, he and the other coders will be back to work on the code.
Jump to: