5bb55b

KASPlex | KRC-20 | HODL

[5bb55b @5bb55b]

https://t.co/v3B4ouNCj7

go-kaspabook is a lightweight indexed kaspa REST-API system suitable for integration with dApps/CEXs/organizations (but not suitable as a data source for browsers).

It is an early version, just about 10 days of work. I need a few more days to test it, then I will use it in several projects and observe how it performs.

The API doc is currently generated by AI, I will optimize it later.

Key features:
Data fetching via Kaspad vspc2 (only focuses on the chain-blocks and the accepted-txns data.);
Using the local RocksDB with support for daascore-to-live pruning;
Using protobuf data format to save disk space;
An aggressive data item storage strategy (more index-params will be added later to support additional data);
Reorg processing mechanism for index-keys.

book-API:
GET - /book/status
GET - /book/vspcs/daascore/:score[?count=10&prev=1]
GET - /book/vspcs/bluescore/:score[?count=10&prev=1]
GET - /book/blocks/:hash
GET - /book/transactions/:txId
GET - /book/addresses/:address/transactions[?daascore|bluescore=12345&count=10&prev=1]

kaspad-API:
GET - /kaspad/addresses/:address/balance
GET - /kaspad/addresses/:address/utxos
POST - /kaspad/transactions
POST - /kaspad/transactions/rbf

[5bb55b @5bb55b]

@Dodo13080274 @ohyishi 开源的话，可以考虑发动一下社区技术力量，把txdata解析部分搞搞。

[5bb55b @5bb55b]

尝试升级到 Go 1.26 ，KRC-20 新节点的各组件运行良好。
得益于 GC 与 CGO 的底层优化，整体性能提升约 10-15% ，Lyncs引擎处理能力约 12K TPS on 16 Cores 。

[5bb55b @5bb55b]

@Valodeous I recall this was a "misunderstanding" caused by different field names in the API. I think we can fix it by adding a set of "v2" APIs (instead of changing the original ones).

[5bb55b @5bb55b]

@Valodeous While not the main point, the top 100 holder statistics have indeed been implemented, if that's what you're referring to. Additionally, KRC-20 nodes will support a debug API, allowing direct access to raw data for all states.

[5bb55b @5bb55b]

KRC-20 is about to reach its next milestone.

[5bb55b @5bb55b]

@kaspador_ No, I can't let you leak any more, hahaha.

[5bb55b @5bb55b]

@supertypo_kas @kaspa_stream @kasfyi Super thanks! Light-node are underway (via the new vspc2), which will allow for low-cost deployment and API compatibility.

[5bb55b @5bb55b]

@coderofstuff_ @IzioDev Fantastic! This will produce a series of chemical reactions. Super thanks @coderofstuff_ @IzioDev

[5bb55b @5bb55b]

@michaelsuttonil @kasplex @Kaspa_KEF @khriskang Thank you very much! I believe this would have been impossible without the help of you and all core members.

[5bb55b @5bb55b]

I don’t know much about Sparkle, but I think it’s a system at different levels. Sparkle looks like a more complex infrastructure at the bottom level, but the Lua-based VM provides a simplified implementation of the application layer. It is lighter and faster than solidity-EVM, but still slower than golang.

[5bb55b @5bb55b]

EVM means a fixed technology path (with bloated compatibility builds), which is certainly true. But we can also explore other possibilities after untying some old shackles. For example, it can easily implement parallel computing, has very simple and easy-to-learn programming syntax, and has relatively faster execution speed, etc.

[5bb55b @5bb55b]

@Dodo13080274 我确实更喜欢轻量级的各种东西😆。

[5bb55b @5bb55b]

If we wrote the contract in Lua.

[5bb55b @5bb55b]

@oneforonehaha @SentinelKaspa @kaspador_ @Kaspa_KEF @kasplex It is still a very early experimental version. As an open SC environment, it still needs at least two modifications to the underlying mechanism, but it is sufficient for the system contract of KRC20. Next, I need to tune the performance.

[5bb55b @5bb55b]

@shit_o_shi As an embedded scripting language, it is very lightweight and fast (with the JIT-compiler). I think that in some specific application scenarios, it is not worth making things too complicated or even creating a new language😃.

[5bb55b @5bb55b]

@michaelsuttonil @skibumtrading I think we can use features of KIP10 (and maybe some additional ones).

[5bb55b @5bb55b]

@coderofstuff_ @michaelsuttonil Ahaha, thank you😆, I might try to make some small functional changes to the node to help understand it.