[FEATURE]: GSoC 2026: An Automated Smart Vault & Oracle Feature for MiniChain

Feature and its Use Cases

Hi! I am Sanaica. I recently finished up my work on PR #67 (Implementing Canonical Serialization and securing the P2P broadcast envelope). For GSoC 2026, I would like to propose a feature built directly on top of MiniChain: An automated Smart Vault.

1. The Idea

It is an automated portfolio management tool that monitors external markets and helps users execute trades on MiniChain. It offers users two modes:

• Signal Mode: The system analyzes market trends and simply alerts the user when there is a high-probability opportunity to buy or sell.
• Auto-Pilot Mode: If the user grants secure permission, the system doesn't just alert them, it automatically constructs and executes the trade on the MiniChain network without the user needing to manually click anything.

2. The Motivation

Right now, MiniChain has a rock-solid, mathematically secure ledger. However, like all blockchains, it is isolated. It does not natively know the real-world price of assets.

If MiniChain is going to support real Decentralized Finance (DeFi) applications, it needs a secure way to fetch external market data and act on it. This feature bridges this gap. It provides the MiniChain ecosystem with a practical, automated financial application that proves the network can handle real-world trading scenarios securely.

3. The Architecture & Process

To keep the system fast and completely decentralized, the process runs entirely through a native Python background service (asyncio daemon). Here is the step-by-step workflow:

• Step 1: Fetching Secure Data (The Oracle)
  If an automated vault relies on just one API for its prices, it becomes vulnerable to hacks or outages. To solve this, the Python service will simultaneously pull live price feeds from multiple independent exchanges (e.g., Binance, Kraken). It filters out any extreme errors or outliers and calculates a safe median average so the vault is always acting on accurate data.
• Step 2: Making the Decision (Predictive Analytics)
  Once the system has a secure price feed, a Python-based data analytics model evaluates the market trends, price action, and volatility. When the market conditions cross a predefined threshold, the engine logically triggers a definitive "Buy" or "Sell" command.
• Step 3: Executing the Trade (Cryptographic Constructor)
  When a trade is triggered, the system does not use a web interface. Instead, it uses the user's locally stored private key to mathematically sign the transaction. It then packages the trade using the strict canonical serialization rules I just implemented in PR #67. This guarantees the automated transaction is perfectly formatted before it is broadcast to the MiniChain P2P network for validation.

Questions for Feasibility

Before I formalize this into my GSoC proposal document, I wanted to get your thoughts:

1. Is the team open to adding an automated trading/oracle application to the GSoC 2026 roadmap?
2. From an architectural standpoint, should this live as an integrated module within the core node software, or would you prefer it structured as an external "client" application interacting with the P2P network?

I'd love to hear the maintainers' feedback on the architecture and if it aligns with your goals for the year! Thank you!

Additional Context

No response

Code of Conduct

• I have joined the Discord server and will post updates there
• I have searched existing issues to avoid duplicates

No implementation files or tests are named. Start by reviewing PR #67 and the existing MiniChain node and P2P architecture, then clarify whether this belongs in core or as an external client. Done means the maintainers agree on the architecture, scope, data sources, permissions, and execution model before implementation begins.