Instant delivery

Lifetime updates

1 domain license

Addonv6.1.7

AI Investments for Bicrypto

Name: AI Investments for Bicrypto
Brand: MashDiv
SKU: ai-investments
Price: 89.00 USD
Availability: InStock

A duration-based investment product where you set the term, the rate and the outcome — and fund it yourself.

4.70302 sales

$89$99Save 10%

You'll also need Bicrypto

On its own, AI Investments for Bicrypto won't work — it only runs if you already own Bicrypto. Open the Requirements tab to see exactly what you need and add it to your order.

See it working Live demo Documentation View on CodeCanyon

Plans you price yourself: profit rate, entry limits, image and description
WIN, LOSS or DRAW is a field on the plan — the book's result is a decision
Terms in hours, days, weeks or months, shared across as many plans as you like
Payout terms snapshotted at purchase, so an edit never reprices a live ticket
An hourly task settles every matured ticket with nobody pressing anything
Locked rows and idempotent credits, so a retry can never pay a ticket twice
Customers cancel before maturity and get the full principal back, with no fee
Capital Deployed states your outstanding liability as a single number
ROI Paid Out, Principal Retained and House Result — the product's own P&L
Settle, cancel or reject any live ticket from the Investment Logs desk
Deleting a plan or duration is refused while any ticket still references it
Fifteen permission keys and an invest_ai verification gate on the purchase

Inside AI Investments

You set the term, the rate and the result

A named plan, a term and an amount out of the customer's platform wallet — and at the end of it a credit back at a rate and an outcome you decided when you built the plan. It installs on Bicrypto core and adds nothing else: no second database, no chain, no external service, and nothing standing between you and the money.

In detail

Your customers commit funds from their platform wallet to a named plan for a fixed term. The principal leaves the wallet immediately, the ticket runs, and when the term is up the platform credits the wallet back at a rate and an outcome you decided when you built the plan. It is an addon on Bicrypto core and adds nothing else — no second database, no on-chain component and no external service to sign up for.

How it works

Nothing trades. There is no model, no strategy, no market data and no order placed anywhere in this addon; "AI" describes how the product is presented to your users, not how the return is produced. Every plan carries a profit percentage and a default result of WIN, LOSS or DRAW, and both are snapshotted onto the ticket at purchase — so editing a plan changes what the next customer gets and can never reprice a deal already struck. One hourly task settles whatever has matured: a WIN credits principal plus profit out of your float, a LOSS keeps part of the principal as platform revenue, and a DRAW returns the principal and nothing else.

The whole configurable surface

Lever	Lives on	Decides
Profit percentage	the plan	the rate settlement pays
Default result	the plan	WIN, LOSS or DRAW for every ticket against it
Min and max amount	the plan	how large a single ticket may be
Durations	HOUR, DAY, WEEK, MONTH	the term, attached per plan
Status	the plan	whether the plan is offered at all

There is no settings screen because there are no settings. The plan row is the configuration, and two plans can be entirely different products.

What operators control

Four admin screens — a dashboard, plans, durations and the Investment Logs desk — behind fifteen permission keys and an invest_ai verification gate. The desk states Capital Deployed, ROI Paid Out, Principal Retained and House Result, and lets an administrator settle, cancel or reject any live ticket through the same code the hourly task uses. Deleting a plan or a duration is refused while any ticket still references it. Customers cancel before maturity and get the whole principal back, with no fee and no penalty.

Nothing trades and you fund every payout, so treat each percentage point you publish as one you are liable for. The plan's maximum caps a single ticket and nothing else — there is no per-user cap and no total-book cap, so Capital Deployed is the only figure that tells you what you owe. The cron process has to be running; ECO tickets also need the Ecosystem addon, while SPOT tickets need nothing extra.

You configure the outcome, and you fund it

Nothing trades. There is no model, no strategy, no market data and no order placed anywhere in this addon — the word AI describes how the product is presented to your users, not how the return is produced. A plan carries a profit percentage and a default result of WIN, LOSS or DRAW, and both are copied onto the ticket at the moment it is bought, so editing a plan changes what the next customer gets and can never reprice a deal already struck. A WIN pays principal plus profit out of your float, a LOSS keeps part of the principal as platform revenue, and a DRAW hands the principal back. That is the whole mechanism, and it is why there is no market risk and no counterparty anywhere in it.

Treat every percentage point you publish as one you are liable for. There is no randomisation and no per-investment override that revises the plan's result — minProfit and maxProfit look like a range the return is drawn from, and nothing reads them.

Every open ticket is principal you are holding

The amount leaves the customer's wallet at purchase and stays off their balance until the term is up, so an open book is money you owe back rather than money you have made. The Investment Logs desk states it as one figure — Capital Deployed — beside ROI Paid Out, Principal Retained and House Result, which together are this product's own profit and loss. Ranked charts show which plans and which markets carry the exposure, computed with the same filter as the headline figure so they reconcile with it exactly.

The plan's maximum caps a single ticket and nothing else: no per-user cap, no daily cap, no total-book cap. A LOSS credits the forfeited slice — the plan's percentage of the principal, not the principal — to the oldest Super Admin's wallet, so if no Super Admin exists that revenue leg is dropped and logged.

Maturity settles itself, and a retry cannot pay twice

One hourly task scans every active ticket, settles the ones whose term has expired and credits the wallet the principal came from. Each payout is written through the wallet service under an idempotency key, the row is locked for update inside the settlement transaction, and the payout reference is unique platform-wide — so a duplicate is read as proof the money already moved rather than as an error to retry. An administrator can settle, cancel or reject a live ticket from the same desk, and both doors run the same code, so they cannot pay differently for the same terms.

Maturity is only checked when settlement runs, so a term is a floor rather than an exact moment and a one-hour ticket can take up to two hours to pay. A customer who opens their own list settles their matured tickets on the spot.

Settling by hand needs one key, and it leaves a record

Fifteen permission keys cover this addon — five verbs on each of tickets, plans and terms — and the doors that settle, cancel, reject or edit a ticket all sit behind the same one, edit.ai.investment. A role without it is refused by the server before the handler runs, so a support account can be given the desk to read and nothing to pay out. Each leg of a ticket is its own row on the customer's wallet ledger: the debit at purchase carries the ticket id, the payout carries that id with _roi on the end, a cancellation carries _refund, and that column is unique platform-wide, which is what makes a payout impossible to write twice. Every change an operator makes on the addon's admin screens is written to the platform's audit trail with who made it, what it touched and whether it succeeded — refusals included, carrying the reason the endpoint gave.

The trail records changes, not reads, and only the ones that reach the endpoint: a request the permission gate turns away is answered 403 and never becomes a row. A Super Admin passes every key by name, so scoping a member of staff means giving them a role that is not Super Admin.

outcomes a plan can settle at: 3
term units, hours to months: 4
the only settlement schedule: 1 hour
permission keys: 15

Everything included

73 capabilities, in 7 areas

Every item below exists in the source you receive. Nothing here is a roadmap.

Plans

The product your customers buy, and every field that defines it.

Named plans, each with a public title and a separate internal name
Profit percentage — the rate every ticket against that plan settles at
Default result per plan: WIN, LOSS or DRAW
Minimum and maximum amount per ticket, enforced server-side
Plan description and uploaded plan image
Trending flag that sorts and filters the plan lists
Active/inactive toggle, flipped in place from the plans table
Terms attached per plan, with the join re-checked at purchase
Create, edit, view, delete, and bulk activate or deactivate
Deletion refused while any ticket still references the plan
Per-plan panel: positions, staked total, paid profit and a count per status

Terms

How long a commitment runs, and how maturity is measured.

Terms in hours, days, weeks or months
Any whole number of units, from one upward
One term shared across as many plans as you attach it to
Maturity derived from the purchase time — no end date to drift
Term picker fed by a pre-formatted options list
Deletion refused while any ticket still references the term

The purchase panel

What a customer sees, on the screen they are already on.

AI Investment tab in the order form on both the standard and Pro trade screens
Plan cards showing the rate, the limits, the term, the description and the image
Trending badge on the plan card
Term selector fed by the plan's own attached terms
Amount field showing the live balance of the market's quote currency
Expected profit computed before the customer commits
A failed balance read shown as a failure rather than as a zero balance
Ecosystem markets marked, and funded from the ECO wallet
Verification notice replacing the form when the purchase gate blocks the customer

Positions and cancellation

The customer's own book, and the one door out of it.

AI tab in the Pro workspace order panel, badged with the running count
Plan, amount, profit, status, age and action per ticket
Outcome, ROI and profit withheld while a ticket runs, and signed once it settles
Cancel a running ticket at any point before maturity
Full principal refunded on cancel — no fee, no penalty, no minimum hold
Own-investment list, paginated up to a hundred rows a page
In-app notification on purchase and on settlement

Settlement

The only automatic money mover in the product, and what stops it paying twice.

One hourly task scanning every running ticket on the install
Matured tickets also settled in-line when the owner opens their list
Manual run from the scheduled-task screen
WIN pays principal plus profit, LOSS keeps part of it, DRAW returns the principal
LOSS payout floored at zero — a customer can never end up owing you
Payout terms snapshotted at purchase and never re-read from the plan
Term precedence: the ticket's snapshot, then the plan, then a DRAW
The ticket row locked for update inside the settlement transaction
An idempotency key per payout, varied by the outcome
A platform-wide unique payout reference, and a collision read as proof the money already moved
Payout routed back to the wallet the principal came from
An unresolvable wallet raises an alert and leaves the ticket running, rather than closing it unpaid
Cancellation and maturity cannot both pay — each re-reads the row under the lock
The platform's own leg booked per settlement: a loss on WIN, revenue on LOSS
A completion email per settled ticket

The operator's desk

Every ticket, what you can do to it, and what the book is worth.

Every ticket in one table: investor, plan, amount, status, profit, market, wallet type, result, term and date
Editing limited to five fields: plan, term, market, profit and result
Amount, owner, wallet type and status refused at the edit door, each with a reason
Settle, cancel or reject one ticket through the same code the hourly task uses
Bulk status change reporting per-ticket successes and failures
Deletion that refunds only when the principal is genuinely still outstanding
Restore of a soft-deleted ticket
Capital Deployed — outstanding principal, as one number
ROI Paid Out, Principal Retained and House Result
Win rate over time, plus winning count, completed count and average ticket
Spot and ecosystem capital by value
Top markets and top plans by deployed capital, on the same filter as Capital Deployed
Dashboard counts by status, by result and by wallet type
Amount-invested chart over one month, three months or a year
Plan distribution computed from real tickets, and the ten most recent purchases
Dashboard refreshing every minute, with a retry card instead of a page of zeros

Access and the money trail

Who may pay a ticket out, and what the ledger says afterwards.

Fifteen permission keys across tickets, plans and terms
A verification gate on the purchase, enforced server-side
A licence gate on every admin screen for the addon
One extension switch that also registers and deregisters the settlement task
A ledger entry for each leg: the funding debit, the ROI credit and every refund
The funding transaction preserved and annotated on cancel rather than destroyed
Three seeded notification templates, each with email, SMS and push toggles
An affiliate reward on every ticket a referred customer opens, when MLM is installed
Every administrative change written to the platform's audit trail, refusals included

Licence: Per-domain extension licence, activated in the extension manager
Requires: Bicrypto core. Wallets, accounts, roles, permissions, verification, notifications and the cron process all come from it — this addon adds no infrastructure of its own.
Runs on: Your existing install. No second database, no chain, no node, no external service and no API key.
Processes: The platform's cron process. Settlement runs there, not on the API process.
Storage: Four tables created on boot: plans, terms, the join between them, and the tickets
Admin surface: 4 screens — dashboard, plans, terms and the ticket desk
Customer surface: One tab in the trade order form on both trade screens
Endpoints: 29 — 5 for the customer, 24 for the operator
Access control: 15 permission keys, plus one verification gate on the purchase
Scheduled work: One task, hourly
Optional integrations: Ecosystem, for tickets funded from an ECO wallet — spot tickets need nothing extra. MLM & Affiliate, to pay a referrer on every ticket a referred customer opens. Neither is required.
Nothing trades: There is no model, no strategy, no market data and no order placed anywhere in this addon. The word AI describes how the product is presented to your users; you set the outcome on the plan and you fund it out of your own float.
No randomisation, no ranged return: Every ticket against a plan settles at exactly the same rate and the same outcome. The plan's minimum and maximum profit fields are stored, shown, and read by nothing.
One rate per plan, whatever the term: A plan pays the same percentage on a one-hour term as on a twelve-month one. A longer term that pays more is a second plan.
No exposure cap beyond a single ticket: The plan's maximum caps one ticket. There is no per-user cap, no daily cap and no total-book cap — Capital Deployed is the only figure that states what you owe.
No fee anywhere: Nothing is charged on opening, on settlement or on cancellation, and there is no early-exit penalty. The economics are entirely the spread between what LOSS plans keep and what WIN plans pay.
A term is a floor, not a moment: Maturity is only checked when settlement runs, so a one-hour ticket can take up to two hours to pay unless its owner opens their list first. A month is 30 days of multiplication, not calendar arithmetic.
Settles once, then ends: Nothing rolls over. There is no reinvestment and no compounding; a customer who wants another term opens another ticket.
The revenue leg needs a Super Admin: A LOSS credits the forfeited slice — the plan's percentage of the principal, which is also what the customer's payout is reduced by — to the oldest Super Admin's wallet. With no Super Admin the customer is still paid correctly, but that revenue is dropped and logged.
No page of its own: There is no landing page, plan browser or portfolio route for this addon. Customers buy from the tab inside the trade workspace, and their own list is in the Pro workspace order panel only.
No settings screen: There are no platform settings rows for this addon and nothing in the environment file. The plan is the entire configuration surface, and the settlement interval is hard-coded.