Introducing Collect-TK: Takamaka’s solution for T-PoS (Takamaka Proof of Stake)


“Proof of Stake (PoS) is more energy efficient”

It is known that the Proof of Stake (PoS) consensus algorithm is more energy efficient compared to Proof of Work (PoW) (used by Bitcoin and other networks), as it does not require miners’ hardware to perform large amounts of computational work, and it is also considered secure, as it is more difficult for a single entity to gain control of most of the network’s assets and therefore the Blockchain.

Collect-tk is a Takamaka solution, created by the engineering team, to support T-PoS (Takamaka Proof of Stake), which uses the Proof of Stake (PoS) consensus algorithm to validate transactions on the blockchain network.

When a miner successfully solves a “problem,” they are rewarded with the Takamaka network cryptocurrency, and their solution is added to the blockchain as a new block. This process is known as Staking. Validators (referred to as “stakers”) are randomly selected to create new blocks and validate transactions, based on the amount of cryptocurrency they hold as collateral.


At the link, you can find the information needed to carry out the project independently, in the example given, note that .tkm-chain and a JSON file (collect_tk_client_config_file.json) with the basic information needed to run it are provided.



Copy code









This JSON file contains the configuration settings for a client interacting with the server, using these settings to communicate via APIs (Application Programming Interfaces).

Here is a brief explanation of each field in the JSON file:

“baseUrlEndpoint”: This is the base URL of the server with which the client communicates.

“requireChallengeApi”: This is the API endpoint for requesting a challenge from the server.

“checkResultApi”: This is the API endpoint for checking the result of a previous request.

“checkClaimingSolutionsApi”: This is the API endpoint for checking the claiming solutions.

“getHexTrxApi”: This is the API endpoint for getting the hexadecimal transactions.

“updateClaimingSolutionsApi”: This is the API endpoint for updating the claiming solutions.

“savePayTodoApi”: This is the API endpoint for saving payment transactions to be processed later.

This JSON file provides the client with the information needed to communicate with the server, so that it can carry out various activities, such as checking results and updating claiming solutions.

The difficulty of block extraction and validation will be directly proportional to the difficulty required to add a new block to the blockchain network, in fact, a higher difficulty means that more computational power will be needed to extract the new block.

Reference procedure is visible at this link:

Do you want to try?

You can refer to the tabs on GitHub:



Additionally, the team’s engineers will be happy to answer your questions, so you can write directly to

For everything else, stay in touch with us