VextaProject/ Vexta
Vexta Vexta-CPU-Miner Vexta-Android-Wallet
Watch
1
0
Fork
You've already forked Vexta
 0
Code Issues Pull requests Projects Packages Wiki Activity Actions
Vexta/src/interfaces
History
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Capri 31e4f44475
 Add post-quantum address selector to desktop wallet
2026-09-01 17:57:42 +00:00
..
chain.h Add post-quantum wallet integration 2026-08-31 19:23:30 +00:00
echo.cpp Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
echo.h Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
handler.cpp Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
handler.h Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
init.cpp Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
init.h Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
ipc.h Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
node.h Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
README.md Initial Vexta Core v0.1.0 release 2026-07-15 14:07:28 +00:00
wallet.h Add post-quantum address selector to desktop wallet 2026-09-01 17:57:42 +00:00

README.md

Internal c++ interfaces

The following interfaces are defined here:

  • Chain — used by wallet to access blockchain and mempool state. Added in #14437, #14711, #15288, and #10973.

  • ChainClient — used by node to start & stop Chain clients. Added in #14437.

  • Node — used by GUI to start & stop digibyte node. Added in #10244.

  • Wallet — used by GUI to access wallets. Added in #10244.

  • Handler — returned by handleEvent methods on interfaces above and used to manage lifetimes of event handlers.

  • Init — used by multiprocess code to access interfaces above on startup. Added in #19160.

  • Ipc — used by multiprocess code to access Init interface across processes. Added in #19160.

The interfaces above define boundaries between major components of digibyte code (node, wallet, and gui), making it possible for them to run in different processes, and be tested, developed, and understood independently. These interfaces are not currently designed to be stable or to be used externally.