See the list of articles here.
🇰🇷: Klaytn State Trie Cache Series #4: Cache Size Tuning 하기

Klaytn has been putting a lot of effort to improve the performance of our blockchain platform. In this series of articles, we want to walk you through the process of enhancing state trie cache performance.

1. Identifying the Cache Problem
2. Searching for the Optimal Cache
3. Calculating state trie cache misses
4. Tuning Cache Size

In our last post, we tested our hypothesis that the factors that influence cache misses are the changing state trie size (TotalAccounts, ActiveAccounts, TPS, trie node size) and cache size. But…

See the list of articles here.
🇰🇷: Klaytn State Trie Cache Series #3: State trie cache miss 계산하기

Improving the blockchain platform has been one of Klaytn’s top priorities. In this series of articles, we would like to walk you through the journey of improving the performance of the state trie cache.

1. Identifying the Cache Problem
2. Searching for the Optimal Cache
3. Calculating State Trie Cache Misses
4. Tuning Cache Size

In our previous post, we compared various caches to come to the conclusion that Fastcache is the most optimal choice for Klaytn. …

See the list of articles here.
🇰🇷: Klaytn 사용성 개선 #2: 플랫폼에서의 멀티시그 지원

One of Klaytn’s top priorities has been improving the usability of our blockchain platform. In this series, we will show you some features that contribute to a more user-friendly experience.

1. Separating Keys and Addresses
2. Introducing Multisig on the Platform-Level
3. Fee Delegation
4. Supporting Role-Based Keys on the Platform-Level
5. Implementing Explicit Types for Accounts and Transactions

In our last post, we learned about separating the key from the address and explained how the key field was added in the process. …

See the list of articles here.
🇰🇷: Klaytn 사용성 개선 #1: 키와 주소의 분리

Improving the usability of our blockchain platform has been one of Klaytn’s priorities. In this series, we would like to show you some of the features that can contribute to improved usability.

1. Separating Key and Address
2. Introducing Multisig on the Platform-Level
3. Fee Delegation
4. Supporting Role-Based Keys on the Platform-Level
5. Implementing Explicit Types for Accounts and Transactions

In this post, we will demonstrate how we can improve usability through separating keys from addresses. Klaytn uses the secp256k1 curve, just like Bitcoin and Ethereum. Account addresses are derived…

See the list of articles here.
🇰🇷: Klaytn State Trie Cache Series #2: 최적의 cache 찾기

Improving the blockchain platform has always been one of Klaytn’s priorities. In this series of articles, we would like to walk you through the journey of improving the performance of the state trie cache.

1. Identifying the Cache Problem
2. Searching for the Optimal Cache
3. Calculating State Trie Cache Miss
4. Tuning Cache Size

In our previous post, we learned that the excessive memory use had been due to a prolonged allocation of a large heap. There are other Go cache options with less GC overhead such…

The English articles will be posted soon. 😉

• Klaytn State Migration: An Efficient Way to Reduce Blockchain Data (한국어, English)
• Klaytn v1.5.0 State Migration: Saving Node Storage (한국어, English)
• Klaytn State Trie Cache Series #1: Identifying the Cache Problem (한국어, English)
• Klaytn State Trie Cache Series #2: Searching for the Optimal Cache (한국어, English)
• Klaytn State Trie Cache Series #3: Calculating State Trie Cache Misses (한국어, English) 🆕
• Klaytn State Trie Cache Series #4: Tuning Cache Size (한국어, English) 🆕
• Klaytn Improving Usability Series #1: Separating Keys and Addresses (한국어, English)
• Klaytn Improving Usability Series #2: Introducing Multisig on the…

Klaytn SDK caver-js v1.6.0이 릴리즈되었습니다.

Caver-js v1.6.0의 caver.abi에서는 Tuple 타입 파라미터에 대한 인코딩/디코딩을 제공합니다. 사용자는 caver.abi에서 제공되는 함수를 사용하여 tuple 타입의 파라미터를 인코딩하거나 디코딩할 수 있으며, 또한 caver.contract를 통해 tuple 타입을 활용하는 Smart Contract를 로딩하여 사용할 수 있습니다.

Tuple 타입 파라미터 인코딩/디코딩

• Caver-js v1.6.0에서는 caver.abi.encodeParameter, caver.abi.encodeParameters, caver.abi.decodeParameter 그리고 caver.abi.decodeParameters를 사용하여 tuple 타입 파라미터를 인코딩/디코딩할 수 있습니다. 또한 caver.contract는 tuple 타입을 사용하는 스마트 컨트랙트를 지원합니다.

Caver-js v1.6.0에 대한 더욱 자세한 설명은 다음 링크를 참고하시기 바랍니다.
https://github.com/klaytn/caver-js/releases/tag/v1.6.0.

Caver-js 패키지는 다음 링크에서 다운로드할 수 있습니다.
https://www.npmjs.com/package/caver-js/v/1.6.0.

Today we are excited to announce that the caver-js (Javascript Software Development Kit of Klaytn) v1.6.0 has just been released.

caver.abi of caver-js v1.6.0 provides encoding/decoding for Tuple type parameters. Users can encode or decode tuple-typed parameters using the caver.abi functions, and also load and use smart contracts using tuple-typed parameters via caver.contract.

Encoding/Decoding tuple type parameters

• In caver-js v1.6.0, tuple type parameters can be encoded/decoded using caver.abi.encodeParameter, caver.abi.encodeParameters, caver.abi.decodeParameter and caver.abi.decodeParameters. In addition, caver.contract supports smart contracts using tuple type.

For detailed information about caver-js v1.6.0, please refer to https://github.com/klaytn/caver-js/releases/tag/v1.6.0.

To download caver-js, please visit https://www.npmjs.com/package/caver-js/v/1.6.0.