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

[jim32]

As i've already mentioned i'm only advisor at Lisk. I don't work for Lisk, just advice them sometimes when i have time and questions from them.

I'm working on my own project right now, i'm going to make announce soon.

Regarding new blockchain for Crypti, i'm not sure it's fair.

Boris, do you will accept Crypti XCR in ICO for your new project "WINGS - Where DAO Unicorns Are Born" ?
What is exchange rate ?

https://bitcointalk.org/index.php?topic=1477055.msg14890777#msg14890777

.

[50cent_rapper]

Has Boris run away

[bitcometrader]

Has Boris run away

I think he went quickly to the LISK-team for a coffee and a bun.

[steve321]

What's the deal with Crypti?  None of the downloads in the instructions work, no docker image to download from within docker, lite client doesn't sync to the blockchain.  Any ideas?

[50cent_rapper]

What's the deal with Crypti?  None of the downloads in the instructions work, no docker image to download from within docker, lite client doesn't sync to the blockchain.  Any ideas?

We are waiting answer from Boris and Crypti team.

Max (Crypti team PR guy) and Olivier (block explorer developer) from Crypti team is now sitting on their own pure Crypti fork called Lisk.

And if you think about it - Lisk is at 25 mil USD marketcap, that means that Crypti fair marketcap is ~ 15 - 20 million. 

[LiskHQ]

Max (Crypti team PR guy) and Olivier (block explorer developer) from Crypti team is now sitting on their own pure Crypti fork called Lisk.

It's not a "pure Crypti fork". 144,000+ lines added speak for themselves.

https://github.com/LiskHQ/lisk/graphs/contributors

[50cent_rapper]

Max (Crypti team PR guy) and Olivier (block explorer developer) from Crypti team is now sitting on their own pure Crypti fork called Lisk.

It's not a "pure Crypti fork". 144,000+ lines added speak for themselves.

https://github.com/LiskHQ/lisk/graphs/contributors

Thank you for link, I've chacked it:

Changing address format.
https://github.com/LiskHQ/lisk/commit/0210b792780cfda27a69a666c931fa6213aea7cd

Revising log messages.
https://github.com/LiskHQ/lisk/commit/95450c7be1a878936ba2fa7418e5d942733278df

Normalising quotes.
https://github.com/LiskHQ/lisk/commit/a4f3e9a414ebf66c684ffa23e5e6aa7389092795

Changing terminology.
https://github.com/LiskHQ/lisk/commit/4a2a09d9617218981b2c7e01012768bf6b874de6

My favorite part:



Even taking into account changing of DB to PostgreSQL the amount of changes is LESS then the amount of changes in Litecoin compared to Bitcoin (different hash function - scrypt).

And you guys manged to gather 10 000 BTC WITH THIS, become a MILLIONAIRES with your premine and even have second trading volume on Poloniex!

Congratulations!

But let's back to talk about Crypti  .

[LiskHQ]

Max (Crypti team PR guy) and Olivier (block explorer developer) from Crypti team is now sitting on their own pure Crypti fork called Lisk.

It's not a "pure Crypti fork". 144,000+ lines added speak for themselves.

https://github.com/LiskHQ/lisk/graphs/contributors

Thank you for link, I've chacked it:

Changing address format.
https://github.com/LiskHQ/lisk/commit/0210b792780cfda27a69a666c931fa6213aea7cd

Revising log messages.
https://github.com/LiskHQ/lisk/commit/95450c7be1a878936ba2fa7418e5d942733278df

Normalising quotes.
https://github.com/LiskHQ/lisk/commit/a4f3e9a414ebf66c684ffa23e5e6aa7389092795

Changing terminology.
https://github.com/LiskHQ/lisk/commit/4a2a09d9617218981b2c7e01012768bf6b874de6

My favorite part:

Even taking into account changing of DB to PostgreSQL the amount of changes is LESS then the amount of changes in Litecoin compared to Bitcoin (different hash function - scrypt).

And you guys manged to gather 10 000 BTC WITH THIS, become a MILLIONARES with your premine and even have second trading volume on Poloniex!

Congratulations!

But let's back to talk about Crypti  .

So you are picking the 4 smallest code changes? 

Here is the changelog from Crypti to Lisk. Cheers!

Binary Install
- Fixed address in use errors on restart.
- PostgreSQL is now included with the “Binary” install, removing the need to install it separately. A simple bash lisk.sh coldstart will initialise the database on first start.
- Running lisk.sh as root is now prevented by default.
- Added lisk.sh reload command. @Isabello
- Fixed #6. lisk.sh restart now cycles both Node.js and Postgresql. @Isabello
- Fixed #10. lisk.sh start/stop/restart now work more reliably. @Isabello
- New simpler binary installation, thanks to liskInstall.sh. @Isabello
- Added tune.sh for optimizing the default postgresql.conf. @Isabello
- Preliminary support for checksummed archives. @Isabello
- Fixed #76. Updating node/lisk-node to 0.12.14.
- Improvements to: installLisk.sh & lisk.sh: @Isabello
    — Reducing ram usage on machines with less than 1024Mb RAM.
    — Made further reliability improvements to process management.
    — Fixing postgresql locale / character encoding issues.
- installLisk.sh - added mainnet vs testnet installation.
- installLisk.sh - laying framework for upgrade support.
- tune.sh - corrected bsd memory allocation.

Front end
- Complete rebranding of the client UI.
- Complete clean-up of the old code base.
- Added translations for 14 languages (Chinese, Russian, German, Dutch, Greek, Spanish, French, Hungarian, Italian, Japanese, Norwegian, Portuguese, Romanian, Ukrainian).
- Enforced BIP39 passphrases.
- Enforced BIP39 second passphrases.
- Unified every modal.
- Improved Dapp registration and Multi-signature registration modals.
- Added fees overview to every modal.
- Added more descriptions to every modal.
- Removed usernames and contacts (to be later reimplemented as a separate Identity Dapp sidechain).
- Fixed several browser specific UI bugs and inconsistencies.
- Improved and unified the overall user interface.
- Fixed #30. Voting now possible after enabling 2nd passphrase @pilldriver.
- Fixed #29. Resetting application state between sessions @2mdoty.
- Fixed #13. Improved error handling when sending transactions @karek314.
- New and improved Russian translation @densmirnov.
- Refactored delegate username validations.
- Fixed non-functioning delegate registration. @2mdoty
- Fixed #34. Dapp registration when 2nd passphrase enabled.
- Fixed #43. Language switcher now works for all languages. @senikk
- Complete change of terminology from dapps to blockchain applications.
- Implemented feeService. Fetching transactions fees for each transaction type.
- Adding security warning before opening apps.
- Closed #9. Disabling buttons on first click. Adding success/error toasts.
- Closed #14. Explaining master passphrase.
- Closed #17. Fixing Safari font-weight / aliasing.
- Fixed #31. Updating bitcore-mnemonic @mrv777.
- Fixed #38. Including total count of delegates.

Back end
- Complete clean-up of the old code base.
- Implemented Forging Rewards with an offset (first week no rewards).
- Changed the transaction fee to a constant 0.1 LISK.
- Revised error and logs messages throughout all backend modules.
- Change of address format (addresses now end with an L).
- Allowing dapps installation from GitHub using https.
- Fixed #13. Checking for presence of recipientId @fix.
- SSL: Using the default cipher from recent nodejs version to protect against weak RC4 cipher @TheGoldenEye.
- Fixed unrecoverable fork when comparing delegate id to generator id.
- Fixed #45. Improved sync / block insertion rate.
- Fixed #3. Setting X-Frame-Options/CSP headers @fix.
- Improved logging of received unconfirmed transactions.
- Improved logging of blocks loading from peer.
- Imposing hard limit on number of transactions per block.
- Changed database engine from SQLite to [PostgreSQL](http://www.postgresql.org/). Providing faster query performance, better support for concurrency, and further options for scalability.
- Removed usernames and contacts from mainchain (to be later reimplemented as a separate Identity Dapp sidechain). Delegate usernames still remain.
- Added dapp zip link storage mechanism, replaces GitHub and Sia integration, with alternative decentralized solutions to be implemented in future releases.
- Implemented concatenated inserts/updates, dramatically reducing number of round trips between client and database: https://github.com/vitaly-t/pg-promise/wiki/Performance-Boost
- Implemented promise based database logic using: https://github.com/vitaly-t/pg-promise
- Added optional PostgreSQL event monitoring using: https://github.com/vitaly-t/pg-monitor (see: config.json:db.logEvents). This will be used for finding further efficiency improvements at the database level.
- Enabled gzip compression on all http requests using: https://github.com/expressjs/compression. Significantly reducing the size of payloads transmitted between peers on the network, and also for lisk-ui (Example: vendor_app.js : Without compression 5.4MB, With compression: 1.2MB).
- Improved syncing reliability and chain comparison efficiency between peers, through query and code refactoring of Blocks#getIdSequence and the /peer/blocks/common API endpoint.
- Accounts#getDelegate(s): Calculating approval rating from total supply rather than a static amount.
- Increased max transactions per block from 10 to 25 (subject to further change after more testing and efficiency improvements have been made).
- Changed peers communication format from CSV to JSON.
- Fixed DApps#getInstalledIds, filtering installed ids to only include numerically named folders.
- Fixed “Dapp not ready” messages when auto-launching dapps upon starting client.
- Closed #24. Changing ‘sync’ to ‘syncing’. @HeisenbergCoin
- Closed #33. Logging each client request. @slasheks
- Fixed #36. Adding username and publicKey properties. @fix
- Fixed #47. Changing timestamps to UTC. @TheGoldenEye
- Fixed #50. Indicating forged blocks more clearly. @punkrock
- Fixed #52. Removing virgin field from mem_accounts. @simonmorgenthaler
- Fixed #54. Restricting total number of votes to 101. @TheGoldenEye
- Fixed #55. Fixing circular reference.
- Updated all 3rd party node modules to latest compatible versions.
- Switched from zip to gzipped tar for release packaging.
- Generated new genesis block for use on open testnet.
- Closed #69. Loading schema using external SQL file @vitaly-t.
- Closed #84. Allowing the setup of logging path in config.json @TheGoldenEye.
- Fixed #77. Peers API endpoint now works when filtered by state @slasheks.
- Fixed all known casting issues caused by db migration.
- Fixed ‘Recipient not found’ error on virgin accounts.
- Improved error logging/comments on fork causes.
- Added proper delegate username validations.
- Fixed test coverage of delegates API.
- Nearly Completed work towards #82, fork cause 3: @karmacoma
    — Heavy refactoring of Round#tick, Round#backwardTick.
    — Memory table updates are now wrapped within db transactions.
    — Added checks for missed/unapplied mem_rounds on startup.
    — Dropping mem_rounds table on reload if not in a valid state.
    — Skipping delegate slot when round is ticking.
    — Don’t receive block when round is ticking.
- Completed work towards #82, fork cause 3: @karmacoma
    — Removing use of setImmediate in round ticks.
    — Scoping each invocation of RoundPromiser.
    — Iterating over delegates asynchronously.
    — Getting outsiders only at end of round.
    — Fixing finishRound logic.
- Fixed pending transactions API endpoint. @fix
- Fixed #8. Delegate usernames must now be lowercase. @fix
- Fixed #40. API payloads are now limited to 2Mb per request. @fix
- Fixed ip address detection when using proxy. @Isabello
- Fixed #122. Corrected schema errors in dapp transfers. @TheGoldenEye
- Fixed #101, #107 productivity calculations. @mrv777
- Fixed #90. Translating ips from long. @cezarsn
- Fixed #131. Added nethash p2p verification. @fix
- Fixed #22. Cannot read property ‘senderPublicKey’ of undefined. @fix
- Fixed forced blocks verification on startup, i.e: config.json-loading-verifyOnLoading.
- Closed #126. Using recommended pg-promise approach. @vitaly-t
- Updated transaction fees. 25 LSK for Delegate and Dapp registrations.
- Change of blockchain application categories
- Moved large queries into postgresql views
- Extracted SQL logic into separate modules
- Closed #134 Adding GET /api/blocks/getFees endpoint.
- Closed #137 Adding GET /api/blocks/getNethash endpoint.
- Standardised and fixed up test-suite.

[50cent_rapper]

So you are picking the 4 smallest code changes? 

Here is the changelog from Crypti to Lisk. Cheers!

What are the 4 biggest code chages

I pointed out that DB change is one of them 

And I'm for the second time offer to speak about Lisk in Lisk thread, this is Crypti thread.

[LiskHQ]

So you are picking the 4 smallest code changes? 

Here is the changelog from Crypti to Lisk. Cheers!

What are the 4 biggest code chages

I pointed out that DB change is one of them 

And I'm for the second time offer to speak about Lisk in Lisk thread, this is Crypti thread.

You started to talk bad about Lisk here.


So if you are not trolling, see you in the Lisk thread.

[50cent_rapper]

So you are picking the 4 smallest code changes? 

Here is the changelog from Crypti to Lisk. Cheers!

What are the 4 biggest code chages

I pointed out that DB change is one of them 

And I'm for the second time offer to speak about Lisk in Lisk thread, this is Crypti thread.

You started to talk bad about Lisk here.


So if you are not trolling, see you in the Lisk thread.

1. I said that Lisk is the fork of Crypti with minimum changes.
2. You post a long change-list.
3. I asked to point to me the 4 MOST IMPORTANT CHANGES in code.
4. You don't want to answer.
Ok.

What is a fair price of Crypti in your opinion compared to Lisk in percentages
I said it is roughly 80% of Lisk price.

And what do you think ?

May be 60% ?

May be 40% ?

[Vega]

What is a fair price of Crypti in your opinion compared to Lisk in percentages
I said it is roughly 80% of Lisk price.

Yes, it seems like fair price for a coin that have no active developer, not even for the effort to even tempfix a bug that makes it possible for anyone to break it in 5 minutes.

[50cent_rapper]

http://www.streetinsider.com/Press+Releases/Bitmain+invests+in+ChainLab,+developers+of+Wings,+to+accelerate+blockchain+innovation/11679658.html

[crypti]

As Lisk holds 80% of Crypti, all the Crypti nodes, and basically continues Crypti in the form of Lisk, these questions should be directed to them. I'm currently 100% focused on my new project Wings.

[freigeist]

As Lisk holds 80% of Crypti, all the Crypti nodes, and basically continues Crypti in the form of Lisk, these questions should be directed to them. I'm currently 100% focused on our new project Wings.

 

hello.

what is wings?!
Can you share the link here, please?!

Thanks.

[50cent_rapper]

What is a fair price of Crypti in your opinion compared to Lisk in percentages
I said it is roughly 80% of Lisk price.

Yes, it seems like fair price for a coin that have no active developer, not even for the effort to even tempfix a bug that makes it possible for anyone to break it in 5 minutes.

Boris said that Lisk team now responsible for the Crypti future.

Can I use my XCR to buy Wings ?

[kenobius]

What is a fair price of Crypti in your opinion compared to Lisk in percentages
I said it is roughly 80% of Lisk price.

Yes, it seems like fair price for a coin that have no active developer, not even for the effort to even tempfix a bug that makes it possible for anyone to break it in 5 minutes.

Boris said that Lisk team now responsible for the Crypti future.

Can I use my XCR to buy Wings ?

What about Wings? Boris also in Wings team.

[50cent_rapper]

What is a fair price of Crypti in your opinion compared to Lisk in percentages
I said it is roughly 80% of Lisk price.

Yes, it seems like fair price for a coin that have no active developer, not even for the effort to even tempfix a bug that makes it possible for anyone to break it in 5 minutes.

Boris said that Lisk team now responsible for the Crypti future.

Can I use my XCR to buy Wings ?

What about Wings? Boris also in Wings team.

I don't know. It's rather quiet here 

[sotisoti]

I asked this question in Telegram a few days ago, the answer from the Wings team was 'probably not'.

[sotisoti]

Who is maintaining the 101 nodes at the moment? Is there a page that shows all the related info?