GX community πππ
Multistaking is a super important KLY feature which allows you to stake any asset to be a staker/validator and protect the whole ecosystem π
In the last commit we finished the system contract which is responsible for onchain stuff related to multistaking.
Details: https://github.com/KlyntarNetwork/KlyntarCore/commit/e6ebfe454f9b0885aca84afcdf49c710e073f265
Multistaking is a super important KLY feature which allows you to stake any asset to be a staker/validator and protect the whole ecosystem π
In the last commit we finished the system contract which is responsible for onchain stuff related to multistaking.
Details: https://github.com/KlyntarNetwork/KlyntarCore/commit/e6ebfe454f9b0885aca84afcdf49c710e073f265
This media is not supported in your browser
VIEW IN TELEGRAM
GX, everyone
We wish you a good weekend before the next important week π§βπ»π§βπ»π§βπ»
We wish you a good weekend before the next important week π§βπ»π§βπ»π§βπ»
β€2
This media is not supported in your browser
VIEW IN TELEGRAM
GX, nerds community πππ
Wake up, wish you a productive day π
Wake up, wish you a productive day π
π₯2
GX, community πππ
Smart Contracts Security
The cybersecurity industry has long had frameworks and classifiers for threats, exploits, typical vulnerabilities, etc. that are used by developers and researchers to make products more secure and quickly respond to incidents.
Such registries include CVSS (v2, v3), EPSS, CWE, CVE, and others.
The crypto industry also has similar registries:
1) Smart Contract Weakness Classification
2) Smart Contract Security Verification Standard by Composable Security
Although today developers have IDEs, AI assistants, and autocheckers that point out errors in the code, sometimes an error can be overlooked, and numerous DEX, liquidity pool, on-chain marketplace, and bridge hacks are proof of this.
That's why we've added SWC and SVSS register work to our roadmap for low-level changes to our WASM and EVM virtual machines to make them more secure πͺ
For example, you can try to start with reentrancy attacks, errors with
Let's tryπ€
Smart Contracts Security
The cybersecurity industry has long had frameworks and classifiers for threats, exploits, typical vulnerabilities, etc. that are used by developers and researchers to make products more secure and quickly respond to incidents.
Such registries include CVSS (v2, v3), EPSS, CWE, CVE, and others.
The crypto industry also has similar registries:
1) Smart Contract Weakness Classification
2) Smart Contract Security Verification Standard by Composable Security
Although today developers have IDEs, AI assistants, and autocheckers that point out errors in the code, sometimes an error can be overlooked, and numerous DEX, liquidity pool, on-chain marketplace, and bridge hacks are proof of this.
That's why we've added SWC and SVSS register work to our roadmap for low-level changes to our WASM and EVM virtual machines to make them more secure πͺ
For example, you can try to start with reentrancy attacks, errors with
tx.origin/msg.sender and othersLet's tryπ€
π3
Daily Tip & Brief Info
GX community!
Mutations - new way for instant network improvements
To improve their projects, crypto projects often use so-called improvements proposals. Ethereum, Solana, TON, Cardano - all of them follow the standard procedure.
But what if we go the other way? What if the process of introducing a new feature, a new virtual machine, or even speeding up consensus could be done instantly? Sounds interesting π€
Our roadmap has a milestone -
This is much easier than trying to understand a large code base of crypto projects.
We're working!
GX community!
Mutations - new way for instant network improvements
To improve their projects, crypto projects often use so-called improvements proposals. Ethereum, Solana, TON, Cardano - all of them follow the standard procedure.
But what if we go the other way? What if the process of introducing a new feature, a new virtual machine, or even speeding up consensus could be done instantly? Sounds interesting π€
Our roadmap has a milestone -
mutations. Using containerization technologies (such as Docker or LXC) we want to speed up the process of introducing new functionality into the network.This is much easier than trying to understand a large code base of crypto projects.
We're working!
GX, everyone
Had a lot of routine these days, sorry for silence
Stay tuned...
Commits speaks for itself π
Had a lot of routine these days, sorry for silence
Stay tuned...
Commits speaks for itself π
Klyntar Community pinned Β«In our Discord channel, we published some kind of high-level information to help you follow the development status π» Visit: https://discord.com/channels/937810185769074718/1256965841375989800/1257232520265601099Β»
GX community π π π
The main subject of today's team call was explorerπ
After meeting we talked about near plans, especially regarding multistaking, codeless smart-contracts, interfaces(wallets+Telegram OpenID to work with codeless smart-contracts via Telegramβ β β )
In previous reports we talked about demos - now it's time for public live
KlyntarScan is live and available hereβοΈ
π± Join us in Discord π π π
The main subject of today's team call was explorer
After meeting we talked about near plans, especially regarding multistaking, codeless smart-contracts, interfaces(wallets+Telegram OpenID to work with codeless smart-contracts via Telegram
In previous reports we talked about demos - now it's time for public live
KlyntarScan is live and available here
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯5
GX community π π π
It's been a few days since our explorer was launched. We want to share some of the resultsπ we managed to track π
We hope you'll find it interesting tooβοΈ
Threadβ€΅οΈ β€΅οΈ β€΅οΈ
It's been a few days since our explorer was launched. We want to share some of the results
We hope you'll find it interesting too
Thread
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯3
So, in more than 2 days of the explorer's work, we managed to:
1οΈβ£ Go through the epoch change process (from 0 to 1) - which means that the validators on the shards changed and the network perceived this event normally βοΈ
2οΈβ£ Process 3.2M+ transactionsπ Before the epoch change, the success rate was close to 100%, we just forgot to disable nonce incrementation for the test environment and therefore, when changing epochs, so the validators continued to add test transactions with false nonce values ββfor test accounts. We will fix this π
3οΈβ£ Managed to test various types of transactions - with Solana-compatible Ed25519 signatures, BLS multi-signatures and, most importantly, transactions with post-quantum signaturesβοΈ . They all work successfullyβοΈ
4οΈβ£ Process almost 400k blocks π . This is more than 100k blocks per shard (for the first testing, a network with 3 shards was launched)
5οΈβ£ The graph of the number of transactions by eras is being built successfully
6οΈβ£ The page with information about the eras also works successfully - you can track the history of the change of eras. Perhaps we should also add a slider to go to the next eras forward, and not just back
7οΈβ£ The page with information about checkpoints will also soon display real data with links to transactions with checkpoints in other blockchains
Next milestonesπΊ :
β‘οΈ More validators, more shards, more power
β‘οΈ New pages on the main site klyntar.org - for multi-staking and codeless RWX smart contracts for the real world. Get your wallets ready
β‘οΈ Preparation for the testnet and bug fix
Join usπ :
π€ Discord
π£ X(formerly Twitter)
Next milestones
Join us
Please open Telegram to view this post
VIEW IN TELEGRAM
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯4
While we are currently very busy before the launch, we're interested in launching decentralized key management solution by Zama to bring the fully homomorphic encryption into our EVM and WASM virtual machines to use FHE on-chain and within Turing-complete logic π§
Already joined the waitlistβοΈ βοΈ
Already joined the waitlist
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯3
GX, community π π©
During development, it is often useful to visualize changes in the chainπ
For example, when launching a private testnet, it would be interesting to know the details of the network operation - created blocks, transaction statuses, validators, shards, and so onπ
That is why we decided to make our explorer open source(here). But in general, there are two reasons:
1οΈβ£ The ability to make changes to the common repository by different developers
2οΈβ£ The ability to simplify the process of development and interaction with the Klyntar network
Therefore, following the link you will see the process of launching a local explorer and a short guide on using it using the example of a local testnet with 1 shard and 1 validator
βοΈ Explore it here
Join usπ :
π€ Discord
π£ X(formerly Twitter)
During development, it is often useful to visualize changes in the chain
For example, when launching a private testnet, it would be interesting to know the details of the network operation - created blocks, transaction statuses, validators, shards, and so on
That is why we decided to make our explorer open source(here). But in general, there are two reasons:
Therefore, following the link you will see the process of launching a local explorer and a short guide on using it using the example of a local testnet with 1 shard and 1 validator
Join us
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯3β€1
Hello, communityπ ha, ha we havenβt posted for a long time because we were busy with development, but lately we have accumulated a lot of material that is worth talking about. Wait)
π3
Scrolling the Twitter(X) π¦ we noticed the post like this. Hope it will be possible for user to return his funds back π
However, this is a good demonstration of why the
On our chain we offer a functionality to fix the state of EVM and WASM contracts in a forkless wayπ¨
In this case(twitter thread) contract is upgradeable, but what if it's not ?
There could also be a situation where complex multi-contract DApps have errors like freezing tokens or native coins and you lose your funds WITHOUT ANY POSSIBILITY OF HELP FROM THE DAPP DEVELOPERSβοΈ π«
So we have to do this so that both developers and average users can be confident in the safety of their fundsπ€
However, this is a good demonstration of why the
state fixing function is needed.On our chain we offer a functionality to fix the state of EVM and WASM contracts in a forkless way
In this case(twitter thread) contract is upgradeable, but what if it's not ?
There could also be a situation where complex multi-contract DApps have errors like freezing tokens or native coins and you lose your funds WITHOUT ANY POSSIBILITY OF HELP FROM THE DAPP DEVELOPERS
So we have to do this so that both developers and average users can be confident in the safety of their funds
Please open Telegram to view this post
VIEW IN TELEGRAM
π3β‘1
Hello community π β
We are publishing the long-awaited tokenomics document which reveals the details - timing, charts, allocation schedules and much moreπ π΅οΈββοΈ
βοΈ All the details are available in our documentation, and we also recommend you to visit the Google Sheet(in docs) for details
π Tokenomics π
We are publishing the long-awaited tokenomics document which reveals the details - timing, charts, allocation schedules and much more
Please open Telegram to view this post
VIEW IN TELEGRAM
π4π1
Good morning/night community π βοΈ
A small comparison table as a demonstration of the importance of developments and improvements!πͺ πͺ
P.S: Have a nice Sunday everyone!π
P.P.S: Bitcoinπ° still not 100K π
Join usπ :
π€ Discord
π£ X(formerly Twitter)
A small comparison table as a demonstration of the importance of developments and improvements!
P.S: Have a nice Sunday everyone!
P.P.S: Bitcoin
Join us
Please open Telegram to view this post
VIEW IN TELEGRAM
π₯2β€1
While reading through a variety of resources as part of education, we found an interesting recent news story about some results in the field of βοΈ :
The
And although it is statedβ€΅οΈ :
This shows progress in research into attacks on symmetric cryptographyπ
Previously, research papers most often encountered and discussed attacks on asymmetric cryptography and signature schemes (including ECDSA, which is used by Bitcoinπ° and EthereumπΉ ), while symmetric ciphers (where the same key is used for decryption & encryption) were considered more resilient π
Sources:
1οΈβ£ Original Paper π
2οΈβ£ Newsweek Article π°
quantum computingThe
Chinese Journal of Computers reported that Chinese researchers from Shanghai University reported using a D-Wave quantum computer to successfully attack three algorithms (Present, Gift-64, and Rectangle) that are critical to the Advanced Encryption Standard (AES), which is used to protect data in government, military, and financial sectors.And although it is stated
The researchers said they had not been able to penetrate AES-256, but had come closer than ever before
This shows progress in research into attacks on symmetric cryptography
Previously, research papers most often encountered and discussed attacks on asymmetric cryptography and signature schemes (including ECDSA, which is used by Bitcoin
Sources:
Please open Telegram to view this post
VIEW IN TELEGRAM
π2