What is Adamant code base?

[AlirezaEthDev]

After reviewing Adamant’s documentation and GitHub repository, I couldn’t quite determine what technology stack the Adamant blockchain uses. I believe it might be built with JavaScript — is that correct?
Could someone please clarify:

1. Which programming languages are used to develop Adamant’s blockchain nodes and smart contracts?
2. What is the virtual machine of Adamant blockchain?
3. What is the exact architecture and transaction flow of the Adamant blockchain?

[adamant-al]

Hey!

Short answer: Yes, ADAMANT’s core blockchain (node) is implemented in JS/TS (Node.js).

1. Languages used

• Blockchain nodes / core protocol: JavaScript (Node.js) (main implementation).
• Client apps / tools / SDKs: JavaScript / TypeScript (and other app-side languages depending on platform, e.g., Swift for iOS/macOS app)
• Smart contracts: ADAMANT does not have a general-purpose smart-contract platform like EVM/WASM chains. Instead, it supports transaction types and application logic implemented at the node + client layer.

So: no Solidity / no on-chain user-deployed contracts in the usual sense.

2. Virtual machine

• There is no VM (no EVM, no WASM runtime) for executing arbitrary smart contract bytecode
• Validation is performed by the node’s core logic for each supported transaction type

3. Architecture and transaction flow

Architecture (typical DPoS-style chain):

• A P2P network of nodes maintains consensus and propagates blocks/transactions
• A set of forging/validator nodes (delegates) produces blocks per schedule
• State is updated deterministically by applying validated transactions in block order

Transaction flow (simplified):

1. Client constructs a transaction (type + payload) and signs it locally with the user’s keys
2. Client broadcasts the signed tx to a node API / network peer
3. Nodes perform basic validation (signature, fees, nonce/sequence rules, payload constraints) and gossip it
4. A forging node includes the tx in a new block
5. The block is propagated, independently validated by peers, and applied to state
6. Client watches for confirmations / inclusion (socket supported for pre-block-included validation state)

Read further:

• Signing transactions: https://docs.adamant.im/essentials/signing-transactions.html
• Encrypting & Decrypting Messages: https://docs.adamant.im/essentials/encrypting-messages.html
• Protocol specification: https://aips.adamant.im/all