Mamont (Drogoz Mamont Finance Technology) is a crypto-financial operations and accounting platform built for companies whose money moves on-chain. It controls the whole chain from a blockchain event to the report — wallet movement, classification, company / employee / expense attribution, the financial ledger, dashboards, reports, CSV exports and the audit log — so that one economic event is never counted as revenue twice.
Deposit flows are read left to right: Deposit → Swap (sent) → After Swap Inbound (came back, on any wallet) → Central Settlement. After swap is a classification mark, not a wallet type, so swapped funds that land on an ordinary Deposit or Central wallet are recognised and excluded from revenue automatically. Exchange deals are accounted separately: what came in for a swap and what went back out — the income is the spread only, never deposit revenue.
Mamont monitors public addresses only — no private keys or seed phrases are ever stored. Blockchain data arrives webhook-first through a provider abstraction (Tatum today), money is Decimal end to end, every financial record is append-only, and a Drog AI assistant acts inside the system exclusively through audited, revertible tools. Inside the app there is also a built-in Team Chat for staff, an in-app notification center, live WebSocket updates and two private Telegram bots.
Mamont is delivered as a packaged installation for one organisation — its own database, wallets, roles, backups and integrations — and the client pays a monthly licence. The price is agreed individually. Access is arranged through Drogoz Network; there is no public sign-up.
| Category Finance |
Status Live |
Bundle Not bundled — private deployment |
Pricing Monthly licence · by negotiation |
- Deposit overview & analytics — revenue, outflow, average per day, best day, deposits per period, inflow vs outflow and cumulative revenue charts.
- Transaction pool — every uncategorised deposit-wallet movement in one place: filter by wallet, asset, amount, date, status, source or link state; select many and classify them together; Manual add and Export CSV.
- Classified transactions & classification history — what was classified, by whom, when, and every revision since.
- Swap chain — Deposit → Swap → After Swap (came back) → Central Settlement, visible as one chain.
- Returned funds (refunds) — refunds tracked per client and deducted from revenue.
- Reconciliation — deposit inflow, minus refunds, minus what the swap consumed, against the settlement that reached Central.
- Exchange & external companies — exchange deals (in for a swap, back out — income is the spread only) and the shares held for external companies, deducted from revenue.
- Deposit wallet monitoring — balances, lifecycle, last webhook, delayed / catch-up state.
- Central pool & overview — central inflow, net flow, settlement from deposits, expenses, affiliate spend, partner payouts, loans issued.
- Auto-classification rules — rules that classify recurring movements automatically.
- Expenses & expense settlement — expense ledger and the settlement of expenses against the central pool.
- Network fees — blockchain fees tracked and set aside separately from revenue.
- Cash & cash-out — cash accounts and a cash ledger; balances are recomputed from entries, never edited by hand.
- Companies, offices, departments — attribution units for every movement, with per-company overviews.
- Employees — accounting entities for attribution and payroll, not logins; effective-dated assignments.
- Payroll — salaries, commission rates, payroll periods, advances.
- Partners, affiliates, loans — business entities, agencies, payouts, spend analytics and loan balances that always agree with their ledgers.
- CSV exports with approval — HMAC-signed, expiring, audited download links; sensitive exports go through the approval workflow.
- Approval workflow — approve / reject / cancel with a comment on every sensitive action (wallet lifecycle, full re-reads, restores, exports).
- In-app notifications — new unclassified transaction, sync error, export ready, approval requested, backup finished, reconciliation done; Seen clears the badge, Read marks the specific entry.
- Telegram bots — external alerts and daily / monthly reports (see below).
- Wallet health — per-wallet monitoring state, last webhook, delayed flags and cursor catch-up.
- Live updates over WebSocket — transactions, dashboard, approvals, wallet health and chat refresh instantly, scoped by permission: a Deposit Assistant receives only its own wallets.
- Comments on transactions — a discussion thread per movement; comments are never deleted.
- Global search — a command palette that finds a hash, a wallet, a comment or a page in one keystroke.
- Roles & permissions — Senior Admin, Finance Chief, Finance Manager, Deposit Manager, Deposit Assistant (only explicitly assigned wallets, enforced by the API), Affiliate Manager — plus per-user permission overrides.
- Audit log — append-only; UPDATE and DELETE are revoked from the application database role, so nothing can be erased.
- User activity — sign-ins, audited actions, comments and navigation (pages, filters, searches) per user, for the Senior Admin.
- Backup / restore — nightly and on-demand backups with checksums and an 18-file accounting CSV package; validated, approval-gated restores.
- System health & settings — maintenance mode, monitoring pause, integrations, provider health,
dmft_verify --strict. - AI assistant — works through the system's own tools with the user's permissions; every action is logged and can be undone.
- Revenue is computed, never stored separately — one selector feeds every dashboard, report, rollup and CSV.
- Financial records are never deleted — they are archived, or a reversing entry is posted.
- Blockchain: public addresses only — no private keys, no seed phrases, ever.
- A manual transaction merges with the automatic one — it is verified, not duplicated.
- A floating button in the bottom-right corner opens an internal chat between employees (not with clients).
- Team board — one shared channel that everyone can read and write.
- Direct messages — one-to-one, visible only to the two participants.
- Instant delivery over WebSocket (
chat.message); an unread badge and a small preview when the chat is closed. - History is loaded from the REST API in pages of 50, so a dropped socket never loses a message.
- Escape steps back: conversation → list → close. Permission:
chat.use. - What it deliberately does not do: it never touches financial records — text only, it cannot change totals; no file or image uploads; no group channels beyond the shared board; messages are capped at 4,000 characters.
- Lives in the right-hand panel and works inside the system: classification, search, reports, creating an employee, and more — in plain language.
- Only with the permissions the user has — a Deposit Assistant asking for “all wallets” sees only theirs.
- Action history and undo — every tool call is stored; mutating actions keep the state they replaced and can be reverted. Irreversible actions are confirmed first.
- Conversation list — past sessions are kept and can be resumed.
- Two private bots — not publicly discoverable; they only talk to Telegram IDs added by an admin. An unauthorised person receives no financial information.
- Deposit Activity bot — new inbound / outbound movements, classifications, daily and monthly deposit reports.
- Central Finance bot — central transactions, expenses, payroll, loans, cash-out.
- Commands —
/start/help/status/today.
- Revenue is derived, never stored — one definition of deposit revenue feeds every dashboard, report, rollup and CSV.
- Movement identity is a fingerprint, not a txid —
sha256(chain|network|wallet|txid|asset|direction|log_index|output_index|trace_index)with a database unique constraint, so webhook retries, rescans and manual entries can never duplicate. - A manual entry merges with later automatic detection — the record becomes manual · auto-verified instead of a duplicate, and the manual audit trail is preserved.
- After-Swap inbound is never revenue — enforced twice: by the category flags and by
classify_movement()itself. - Money is
Decimalend to end — cryptoNUMERIC(78,30), USDNUMERIC(38,8), ratesNUMERIC(38,18); the verification command asserts no float column exists with a money-like name. - Event-time value is frozen — a deposit received when BTC was $100,000 keeps that accounting value forever; live market value is computed separately and labelled as such.
- Cash changes only through the ledger —
post_entry()is the only writer; entries are never deleted, corrections post a reversing entry. - Nothing financial is deleted — users, employees, companies, partners, categories and wallets are deactivated or archived, never removed.
- Provider abstraction — business logic never calls a chain API directly;
BlockchainProviderdefines monitor, sync, transaction, balance, address validation, explorer URL and health, with Tatum and Mock implementations. - Multi-chain — EVM chains via the v4 Data API, Bitcoin-like chains via UTXO inputs/outputs, Tron via native and TRC20 endpoints.
- Webhook-first monitoring with credit discipline — cursor-based catch-up only for delayed wallets, bounded gap repair, checkpointed Force Sync, approval-gated full re-reads, and a provider call log so credit usage is always visible.
- Shared API key safety — Mamont records every subscription it creates and only ever removes its own; another system's subscriptions on the same key are never touched.
- Hash-level duplicate protection —
GET /wallets/{id}/check-txidchecks a hash live before a manual entry is even submitted; a duplicate is rejected with409 duplicate_transaction. - Webhook trust model — a random token in the path, HMAC verification when present, and ingestion that re-reads the transaction from the provider, so a forged webhook can cause an extra read but never a fabricated movement.
- Hardened by default — HttpOnly/Secure/SameSite session cookies, CSRF on every unsafe method, Argon2 hashing, lockout, no public registration anywhere (asserted by tests), object-level wallet permissions in every queryset, append-only audit log, HSTS/CSP/security headers, rate limiting.
- Verifiable operations —
dmft_verify --strictchecks services, migrations, indexes, audit immutability, the role matrix, decimal money columns, provider health and ledger balances.
| Delivery | Mamont is handed over as a packaged installation for one organisation — its own database, wallets, roles, integrations and backups. Nothing is shared between clients. |
| Licence | The client pays a monthly licence for as long as the system is in use. |
| Price | By negotiation — depends on the organisation, the number of wallets and chains, and the integrations required. |
| Access | No public sign-up. Users are created by the Senior Admin; Telegram bots only talk to IDs added by an admin. |
| Source code | Private repository; the client receives the packaged build, updates and support. |
| Layer | Technology |
|---|---|
| Frontend | SolidJS 1.9 · TypeScript (strict) · Vite 6 · Solid Router · TanStack Query/Table · Chart.js · Lucide |
| Backend | Python 3.12 · Django 5.1 · Django REST Framework · Channels (ASGI) |
| Data | PostgreSQL 16 · Redis 7 |
| Background | Celery worker + Celery Beat (database scheduler) |
| Serving | Gunicorn with Uvicorn workers behind Nginx · TLS via Let's Encrypt |
| Blockchain | Tatum (v4 Data API, v3 chain APIs, v3 webhook subscriptions) behind a provider abstraction |
| AI | Drog AI assistant via tool use — Celery-run turns, results pushed over the events socket |
| Quality | pytest (incl. 16 required accounting scenarios, exact money assertions against a mock provider) · vitest · ruff · tsc --noEmit · GitHub Actions CI |
Real screenshots from a Mamont installation (Senior Admin view). Every installation is delivered to one organisation, so the interface you see is what your team gets.
 Sign in — no public registration; every account is created by the Senior Admin |
 Senior Admin dashboard — net operating result, deposit revenue and outflow, exchange profit, network fees, central inflow / outflow, payroll, loans; deposits summary below |
 Deposit transaction pool — every uncategorised movement with wallet, asset, USD at event, classification and confirmation status; Manual add and Export CSV |
 Transaction drawer — full movement detail, linked transfers and the classification picker (swap, transfer to Central, internal transfer, refund, exchange return…) |
From a blockchain event to an audited report
%%{init: {'theme': 'dark', 'themeVariables': { 'primaryColor': '#1a1a1a', 'primaryTextColor': '#ffffff', 'primaryBorderColor': '#c9a855', 'lineColor': '#c9a855', 'secondaryColor': '#0d0d0d', 'tertiaryColor': '#0d0d0d', 'clusterBkg': '#0d0d0d', 'clusterBorder': '#404040', 'edgeLabelBackground': '#0d0d0d', 'fontFamily': 'Inter, Segoe UI, sans-serif' } } }%%
flowchart LR
A["Blockchain event<br/>webhook-first · Tatum provider"] --> B["Wallet movement<br/>fingerprint = sha256(chain|wallet|txid|asset|dir|indexes)"]
B --> C["Classification<br/>revenue · refund · swap · after-swap inbound · transfer"]
C --> D["Attribution<br/>company · employee · expense"]
D --> E["Financial ledger<br/>Decimal end to end · append-only"]
E --> F["Dashboards & reports"]
F --> G["CSV exports<br/>HMAC-signed · approved"]
G --> H["Audit log<br/>UPDATE / DELETE revoked"]
subgraph Deposits["Deposit flow — one economic event, counted once"]
direction LR
P["Deposit"] --> Q["Swap (sent)"] --> R["After Swap Inbound<br/>never revenue"] --> S["Central Settlement"]
end
C -.-> Deposits
| 🏦 Finance teams paid on-chain Deposit revenue, refunds, swaps and central settlement reconciled every day — with the numbers guaranteed to agree across dashboards, reports and CSV. |
🧮 Accountants & auditors An append-only audit log, frozen event-time valuations and Decimal money columns make every figure traceable to a blockchain event. |
| 🏢 Multi-company groups Companies, offices, departments, employees and external companies attributed per movement; role-aware dashboards for each level. |
🤝 Affiliate & partner operations Agencies, payouts and spend analytics next to the revenue they generate; loan and cash balances that always match their ledgers. |
| 🛡️ Security-conscious operators Public-address monitoring only — no keys, no seed phrases — behind server-side authorization and approval workflows for sensitive actions. |
👥 Distributed finance teams Team Chat for staff, comments on every transaction, in-app notifications and Telegram bots keep the whole team on one page — without leaving the system. |
Mamont is a private, per-company deployment on a monthly licence. It is delivered as a packaged installation for one organisation — its own database, wallets, roles, integrations and backups — and the client pays a monthly licence for as long as the system is in use. It is not listed in the public catalogue and is not part of any bundle. The price is agreed by negotiation: contact @drogoz on Telegram or write to hello@drogoz.network.
A live demonstration is 100% free on every product.
See Mamont in action before you commit — our agent gets in touch and walks you through a live demonstration.
Registration is handled by our team — get in touch and receive personal access.
| Channel | Link |
|---|---|
| 🌐 Website | — (private deployment — access is arranged individually, see Pricing) |
| 📄 Details page | — not in the public catalogue (private deployment) |
| 🔒 Source code | deepdrogo/mamont_technology — private repository (Python · TypeScript); this public repo documents the product only |
| @drogoz | |
| 🏛️ Drogoz Network | drogoz.network · Services · Packages · Pricing · Presentation |
| ⚖️ Legal | Terms of Service · Acceptable Use · Privacy · Refunds · Disclaimer · Compliance |
| 🐙 GitHub | deepdrogo |
Made by Drogoz Network
One network — all your services · Premium SaaS Network
More from the network: Drog AI · MyMask AI · Replika · Lidaro AI · IMPERATORI · ZOI Talks · RiderSwap · HyperBlast AI · VerifHub AI · Vadira · Skriper · MyTasker · DrogScan
© 2026 Drogoz Network. All rights reserved. Provided strictly for lawful use — see the Legal Center. Each user is solely responsible for how they use the software.