A complete overview of the AI systems, blockchain architecture, security framework, DAO governance layer, and the full AiBlockcore technical stack.
AiBlockcore embeds machine learning and AI-driven automation directly into the protocol layer. Intelligence is not a feature — it is foundational, operating across every ecosystem module in real time.
Statistical modelling over on-chain event streams for forecasting and trend detection.
Self-adapting automation that replaces static rules with continuously-learned models.
Continuous anomaly detection using supervised and unsupervised classification models.
High-throughput ingestion, normalisation, and feature extraction from blockchain events.
Adaptive parameter tuning to maintain performance, security, and efficiency at scale.
Context-aware recommendations embedded natively in governance and operational workflows.
Built natively on Binance Smart Chain (BSC), AiBlockcore leverages the EVM-compatible, high-throughput blockchain for immutable transaction recording, smart contract execution, and trustless asset management.
| Parameter | Value | Notes |
|---|---|---|
| Network | Binance Smart Chain (BSC) | Mainnet |
| Chain ID | 56 | EVM-compatible |
| RPC Endpoint | bsc-dataseed.binance.org | Public node |
| Asset | USDT (BEP-20) | Tether, 18 decimals |
| USDT Contract | 0x55d398...3197955 | Official BSC USDT |
| Block Time | ~3 seconds | Average |
| Wallet SDK | WalletConnect v2 / Reown AppKit | 100+ wallets supported |
| ethers.js | 5.7.x | Transaction signing & RPC |
Client sends `transfer()` call to USDT contract — wallet signs on-device
Server validates format, checks for duplicate txhash in `deposits` table
`eth_getTransactionReceipt` — confirms inclusion in a block
Validates: `to == treasury_wallet`, `amount == expected`, `contract == USDT_CONTRACT`
All DB operations wrapped in a PDO transaction — atomic and rollback-safe
AiBlockcore uses cryptographic wallet signatures as the sole authentication mechanism. No email addresses. No passwords. No centralized identity store. Your wallet is your identity.
User connects a BSC wallet via MetaMask injection or WalletConnect v2 QR/deep-link.
Server generates a one-time cryptographic nonce bound to the wallet address and session.
User signs a human-readable login message containing the nonce — entirely on-device.
Server uses `ecrecover` to derive the signer address from the signature and nonce.
If the recovered address matches, a secure PHP session is issued with `SameSite=Strict, HttpOnly` cookies.
New wallets receive a unique `AB00001`-format UID. Returning wallets resume their existing session.
AiBlockcore's security model is zero-trust by default. Every input is validated. Every privilege is explicitly granted. Every transaction is independently verified on-chain.
Per-request CSRF tokens injected as meta tags and validated on all state-changing server requests.
Per-IP and per-wallet request throttling persisted in the `rate_limits` table with automatic cleanup.
100% PDO prepared statements. No dynamic query building. No raw string interpolation in SQL.
All output passed through `htmlspecialchars()` via the `h()` helper. Content-Security-Policy headers enforced.
HttpOnly, SameSite=Strict, Secure cookies. 2-hour session lifetime. Custom session name `aibc_sess`.
Transaction receipts fetched directly from BSC RPC. Amount, recipient, and contract address all verified server-side.
`.htaccess` blocks direct HTTP access to `config.php`, `functions.php`, and `cron.php`.
X-Content-Type-Options, X-Frame-Options, X-XSS-Protection, Referrer-Policy, Permissions-Policy all set via `.htaccess`.
| Control | Implementation | Standard |
|---|---|---|
| Input Validation | Server-side on all POST parameters | OWASP A03 |
| Auth | Cryptographic wallet signature | EIP-191 |
| Session | PHP sessions, HttpOnly, SameSite=Strict | OWASP A07 |
| Database | PDO prepared statements only | OWASP A03 |
| Output Encoding | htmlspecialchars on all user-derived output | OWASP A03 |
| CSRF | Synchronizer token pattern | OWASP A01 |
| Rate Limiting | DB-persisted per-IP throttle | OWASP A04 |
| Duplicate Prevention | UNIQUE DB constraints on txhash, cron runs | Data Integrity |
The AiBlockcore DAO layer enables wallet-verified participants to engage in decentralized governance, protocol decisions, and ecosystem coordination — fully on-chain and transparent.
Proposal creation and voting mechanisms recorded on-chain for full auditability.
DAO membership verified via on-chain USDT transaction. Non-custodial and trustless.
Decentralized treasury with multi-signature controls and transparent fund allocation.
Community-driven proposal and ratification process for ecosystem parameter changes.
Cross-participant decision-making without central coordinators or intermediaries.
All DAO activities, votes, and outcomes accessible on the public BSC ledger.
AiBlockcore automates all time-sensitive operations via a secured cron processor. Automation is duplicate-proof, rollback-safe, and independently auditable.
All active investment packages processed daily. UNIQUE constraint on `(package_id, roi_date)` prevents duplicate crediting.
Team structure and leg volumes evaluated nightly; salary level status updated atomically.
Partner matrix positions evaluated and rewarded per cycle. Duplicate guard via `(matrix_id, earn_date)`.
Active DAO members credited to their DAO wallet daily. `(user_uid, earn_date, earn_type)` UNIQUE prevents double-runs.
Recursive BFS team volume calculations cached for performance. Refreshed each cron cycle.
Every cron type timestamped in `cron_log` with `(cron_date, cron_type)` UNIQUE — prevents double-execution across instances.
A phased, milestone-driven development plan with clear technical deliverables for each stage of the AiBlockcore infrastructure build-out.
| Phase | Milestone | Deliverables | Status |
|---|---|---|---|
| Phase 1 | Core Infrastructure | Database schema, PHP 8.2+ stack, security baseline, business logic layer | Complete |
| Phase 2 | Wallet Integration | WalletConnect v2, MetaMask, BSC RPC, USDT verification, clean-URL routing | Complete |
| Phase 3 | DAO Expansion | DAO membership contract, governance protocol, DAO treasury module | Live |
| Phase 4 | AI Ecosystem Deployment | ML pipeline integration, predictive analytics API, AI decision engine go-live | Upcoming |
| Phase 5 | Cross-Chain Integration | ETH / Polygon bridge, multi-chain asset routing, cross-chain identity resolution | Upcoming |
| Phase 6 | Global Scaling | CDN-distributed infrastructure, open-source SDK, enterprise API gateway | Planned |
All platform operations are designed for transparency and independent verifiability. On-chain records are permanent and publicly accessible on BSC block explorers.
Every deposit transaction is permanently recorded on BSC. Anyone can independently verify amounts, addresses, and block confirmations via BscScan.
Unified `transactions` ledger records every credit and debit. Immutable reference for all balance operations.
Timestamped cron run history with success/failure status. `cron_log` table enables full automation audit trail.
Rate limit events and failed authentication attempts logged with IP addresses for security review.
Core API endpoints, DB schema, and wallet integration specs documented and available for technical review.
UNIQUE database constraints prevent duplicate cron processing, duplicate deposits, and duplicate reward credits at the DB level.