Abstract · A foundation for every idea
Ghesis turns a stock investment idea into an explainable research portfolio. Start with a view, connect it to companies and ETFs in a sourced catalog, assign weights, and review the reasoning. Edit, save, or publish a fixed version, then request a quote for its tokenized stocks on BNB Smart Chain.
The product provides three distinct experiences: portfolio research, BSC token trading, and independent BNB reserve shares. Research describes a proposed allocation. BSC token purchases deliver tokens to your wallet. BNB reserve shares hold native BNB and redeem at a fixed rate; the associated asset list remains research information.
Research puts stocks first: five company stocks and one ETF have verified BSC token deployments, alongside ten crypto assets. Three stock themes lead the nine curated themes. Portfolios contain 5–10 holdings with individual weights of 1%–50%, totaling 100%. These limits help inspect allocations; they do not establish investment performance.
This paper explains what each step produces, how users can verify it, and where the product’s limits remain. Ghesis does not promise returns or price stability. The reserve contract has not been independently audited, and a verified deployment is not an audit of its safety.
| Experience | What you can do | What it means |
|---|---|---|
| Research | Generate, edit, analyze, save, and export a portfolio | An allocation and reasoning for your review; no trade is placed |
| Publish | Preserve a fixed version and its content hash | A permanent link within the site’s access settings |
| BNB reserve shares | Create a token, deposit BNB, and redeem shares | Native BNB reserves with fixed 1:1 redemption; no portfolio token holdings |
| BSC token trading | Get quotes, buy a portfolio, or sell one asset | BSC tokens are delivered to your own wallet |
| Future multi-asset reserves | A separate research direction | Multi-asset-backed fund shares and automatic rebalancing are not available |
01 · From a view to a portfolio
An idea such as “AI demand connects chips, cloud platforms, devices, and automation” leaves decisions open. Which companies are relevant? How should capital be divided? What evidence would change the view? Ghesis makes these decisions visible before a user chooses to trade.
Portfolio construction has four separate questions: whether the idea is understood, whether the asset identity is correct, whether the weights express the intended tradeoffs, and what the user actually receives. Research can help with the first three. The final question requires transaction records and actual balances.
The goal is a portfolio that is understandable, editable, and traceable. Each holding includes reasoning. Users can change the assets and weights. The method and catalog snapshot identify how a version was created. A persuasive explanation is still something to check, not proof of a sound investment.
A portfolio can contain several companies or protocols exposed to the same demand cycle, funding conditions, or interest rates. Holding limits and concentration metrics do not establish diversification or suitability. The user remains responsible for assessing the thesis, valuation, time horizon, and ability to bear losses.
02 · Research, publishing, and ownership
The research flow takes an idea and a selected method, builds a proposed portfolio, and validates its tickers and weights. The resulting record contains a name, original thesis, theme, research note, and holdings with individual reasons. A budget breakdown multiplies the budget by each target weight; it is not a market quote.
Saving and publishing serve different purposes. A draft belongs to the current browser session. A saved portfolio remains in that browser and can be exported. Publishing stores a fixed version under the signed-in account, including the asset reference snapshot, publication date, and content hash. Later edits do not overwrite a published version.
Token creation starts from a publication. The publisher chooses the network, name, symbol, and deploying wallet. The wallet sends a contract creation transaction after user confirmation. Ghesis verifies the transaction, deployed code, and configuration before associating the token with the publication.
Stock-token trading uses PancakeSwap V3 on BSC; crypto-only trades retain Uniswap V3. Quotes bind the wallet, venue, amount, routes, minimum outputs, and expiration. Ghesis checks the receipt and assets received. Tokenized stocks depend on issuer terms and do not automatically confer direct share ownership or shareholder rights. Trading does not change a BNB reserve token into an asset fund.
| Step | Input and output | User action |
|---|---|---|
| Research | Idea → assets, weights, and reasoning | Review and edit |
| Save | Allocation → browser record or exported file | Keep a copy |
| Publish | Reviewed allocation → fixed version and link | Sign in and publish |
| Create token | Publication → verified reserve contract | Choose a network and confirm in wallet |
| Deposit or redeem | BNB ↔ fixed number of shares | Confirm each transaction |
| Trade | Quote → BSC tokens or BNB in your wallet | Review the quote and confirm |
Define a thesis
Select a research method
Asset identity and weight limits
Refine assets and weights
Keep a portfolio copy
Research creates a portfolio you can review. It does not require a wallet signature or move assets.
Explore each path. A research allocation is an input to trading, not proof of a completed purchase.
03 · From an idea to candidate assets
Ideas may contain 4–500 characters. AI research interprets the idea and its constraints against the fixed asset catalog, then proposes 5–10 holdings. Names, themes, notes, and holding explanations are generated in English. The original user input remains part of the portfolio record.
The curated method offers three stock themes first: US stock leaders, AI platforms, and an S&P 500 ETF core with a technology stock tilt. Six crypto themes remain available separately. Keyword matching selects a starting allocation; its score is not investment confidence. AI is instructed to use stocks and ETFs for general stock ideas and only select crypto when requested.
If no theme matches, 5–10 recognized tickers can create an equally weighted custom portfolio. When a theme matches, review the resulting list rather than assuming every ticker in the input was included. Equal weighting is a starting point for editing.
Curated theme matching cannot reliably interpret exclusions, negation, or short positions. It asks the user to describe a positive theme and then edit the holdings. AI is instructed to respect exclusions and decline ideas that cannot be expressed with the available catalog.
AI output is validated for known tickers, duplicates, holding count, weight limits, and a 100% total. The model cannot choose contract addresses or initiate transactions. These checks validate the portfolio’s format; users must still review the company or protocol connections and assumptions. If AI is unavailable, curated themes remain a separate option.
“BSC activity connects
trading and lending.”
Start with a change you believe in. Research connects that idea to relevant companies.
Select a step to explore the curated BSC portfolio.
04 · Asset identity and availability
The catalog includes NVDAon, AAPLon, GOOGLon and SPYon from Ondo, plus AMZNx and TSLAx from xStocks on BSC. Display tickers NVDA, AAPL, GOOGL, SPY, AMZN and TSLA identify the underlying security; execution uses the specific issuer token address. Official issuer lists, onchain symbols and 18-decimal precision were checked on September 18, 2026. Ten existing crypto tokens remain available. Ondo token list, xStocks token list.
All new transactions use BNB Smart Chain mainnet, chain ID 56. Native BNB pays network fees and funds purchases and reserve deposits. Binance-pegged ETH is a separate BEP-20 token; it is not the native currency. Network configuration
Stock tokens represent issuer-defined economic exposure and may carry eligibility, jurisdiction, transfer and redemption restrictions. They are not automatically equivalent to directly owned shares. Company and ETF risks coexist with issuer, custody, smart-contract and liquidity risks. Read the applicable issuer terms before trading. Crypto representations may also depend on an issuer, custodian or bridge.
A reserve contract preserves BSC asset addresses and weights as research references. It does not purchase the assets or track their prices. Historical publications from another catalog cannot create BSC reserves or be reused as BSC trades.
Before quoting, the app checks the BSC chain, pinned protocol bytecode, token metadata, reference freshness, available V3 liquidity and price impact. Catalog membership does not guarantee an executable route.
05 · Token quantities and reference prices
Native BNB, WBNB and Binance-pegged ETH are distinct assets. The router wraps BNB for swaps and unwraps WBNB when selling tokens back to BNB. Token quantities use integer base units; the current catalog contains only 18-decimal tokens.
Underlying stock bid and ask prices come from Robinhood public stock reference data, in USD per underlying share. They are shown separately from BSC token quotes. Robinhood token deployments and multipliers are not applied to Ondo or xStocks tokens. Ghesis does not calculate stock-token NAV or corporate-action conversion ratios. Reference API
Crypto references use Binance spot bid and ask prices in USDT; BTCB maps to BTCUSDT. Neither stock nor crypto references determine the executable BSC price. References are fetched on load or refresh with timestamps. Missing, halted or stale data pauses new quotes; there is no promise of continuous availability outside underlying market hours.
References use timestamped market data and reject missing, stale, nonpositive or crossed prices. The quoted onchain output can differ from the underlying market because of pool liquidity, peg differences, fees and slippage.
Reference prices do not determine BNB reserve redemption. Reserve shares redeem native BNB at a fixed one-to-one rate in base units.
06 · Weights and allocation rules
Research weights use integer basis points. One basis point is 0.01%; 100 basis points equal 1%. Each portfolio has 5–10 holdings, each weighted from 100 to 5,000 basis points, with a total of exactly 10,000.
When a user changes one weight, that value is fixed and the other holdings share the remainder. The algorithm respects each holding’s minimum and maximum. It resolves rounding in integer basis points so the result totals exactly 100%.
The editor accepts percentage weights with up to two decimal places. Removing an asset must leave at least five holdings; adding an asset cannot exceed ten or duplicate an existing ticker. These constraints describe the product format and do not validate an investment strategy.
Concentration uses HHI = Σ(wᵢ / 10,000)². Effective holdings equal 1 / HHI. Six equal positions have an effective holding count of six. These measures describe weight concentration only; they exclude correlations, volatility, and returns.
6.1 Allocation mechanics
The algorithm first checks that the amount to distribute can fit every minimum and maximum, and that scores are finite and nonnegative. It reserves the minimum for each holding, then allocates the remainder proportionally. If all scores are zero, it uses equal proportions.
Any holding that would exceed its cap is capped first. The remainder is recalculated across the other holdings. Once no cap is exceeded, ideal allocations are rounded down, then leftover basis points are assigned in descending order of fractional remainder. Ties use the original holding order.
6.2 A reproducible calculation
An equal allocation across six holdings produces four weights of 16.67% and two of 16.66%, totaling 100%. Fixing one at 25% leaves 75% for the remaining five. Their starting proportions and the weight limits determine the final allocation.
The interactive figure below always calculates from the same baseline, allowing adjustments to be compared without depending on previous slider movements.
6.3 A starting point, not an optimum
Curated and equal-weight allocations make tradeoffs visible. They are not optimized against historical returns, a risk model, or current valuations. Users can revise them after reviewing the thesis and holdings.
Explore how allocation works. The weights are not a recommendation; each adjustment starts from the same baseline for comparison.
07 · Reasoning and research sources
A holding’s explanation should describe its connection to the thesis and the assumptions that need checking. A statement that a company sells relevant equipment is different from a claim about current orders, market share, or future returns.
Curated portfolios use human-written theme frameworks. Custom portfolios begin with user-selected tickers. AI portfolios record the model and catalog snapshot alongside the output. These methods remain identifiable rather than being presented as interchangeable evidence.
AI research does not browse the web for current facts. It can misunderstand constraints or provide incomplete, outdated, or incorrect business reasoning. Review the protocol’s own disclosures and the current situation before acting.
Catalog validation confirms recognized tickers and configured addresses. Publication hashes identify a fixed record. Transaction verification checks an onchain operation. None of these alone proves the author’s identity, research quality, or investment performance.
Local and imported files can be edited. Published versions preserve the submitted content, while the original research remains the user’s responsibility. A successful generation or valid allocation is not a backtest or an audited performance record.
08 · Drafts, revisions, and publications
A portfolio begins with an idea or curated theme. The detail page shows the thesis, holdings, reasoning, and concentration. The editor changes the name, assets, and weights while preserving the original input.
Drafts remain in the current tab’s session. Saving keeps the portfolio in the same browser and makes it available to other tabs on the same site. Clearing browser data can remove both saved portfolios and revision history. Export important work to keep an independent copy.
Saving a curated portfolio creates your own portfolio identity. Later saves update that local portfolio and record actual changes. The history keeps up to 20 recent revisions per portfolio, including name, thesis, added or removed assets, and changed weights.
Publishing requires a signed-in account. The service validates the allocation again and preserves its assets, weights, research content, asset addresses, and catalog timestamp. It assigns a publication date, content hash, and permanent link. The publication remains subject to the site’s access settings.
Editing a publication creates a new version; it does not rewrite the original. Publishing by itself does not create a blockchain transaction, buy assets, or issue shares. The publisher can proceed to token creation from the published page.
An export contains research information and relevant source records. It is a backup and review aid, not proof of a trade. Removing a browser copy does not remove a published version or onchain data.
| Record | Where it is kept | What it preserves |
|---|---|---|
| Draft | Current browser tab | Unsaved research allocation |
| Saved portfolio | Current browser | Allocation and recent revisions |
| Export | A file you keep | Research, asset references, and available history |
| Publication | Your site account | Fixed content, hashes, and publication date |
| Onchain record | Selected blockchain | Contract configuration, transactions, and balances |
Explore your portfolio
Your draft remains available when you refresh this tab. Save, publish, or export it before closing the tab or clearing browsing data.
Saved revisions, publications, and onchain receipts each record a different step. Publishing does not send a blockchain transaction.
09 · Your data and wallet
Browsing themes and editing research do not require a wallet. Saving a portfolio stores it in your browser. Publishing uses your signed-in site identity and preserves the submitted research on the service.
When you use AI research, your original idea and the public asset catalog are sent to Alibaba Cloud Model Studio in the Beijing region. The research request does not include your site identity, wallet address, private keys, transaction history, or balances. Avoid putting confidential information in a prompt. Curated theme matching does not send the idea to the AI service.
The service records usage and active requests to manage availability. AI availability may change, and a failed request may need to be retried later. Curated research remains available independently.
Connecting a wallet provides its address and current network. Creating tokens, approving assets, buying, selling, depositing, and redeeming each require a separate wallet confirmation. Ghesis does not receive private keys or sign transactions on the user’s behalf.
Trading uses the wallet and account associated with the quote. Pending and completed trade records remain with the signed-in account so an interrupted operation can be recovered. Browser storage may also retain pending transaction details.
Published research and onchain metadata have different visibility. Site access settings control the website and its APIs; they do not make blockchain data private. Contract names, symbols, publication references, addresses, and weights can be publicly read on the selected network.
A reserve contract records a publication reference and research allocation. Consider whether you want that information onchain before confirming creation. Blockchain records cannot be removed by deleting a browser copy.
10 · BNB reserve shares
ThesisReserveToken is an independent ERC-20 share contract backed by native BNB. The name, symbol, creator, publication hash, asset address references, and research weights are set at creation. Those assets are metadata; the contract does not purchase, custody, or rebalance them.
The contract starts with zero shares and a zero BNB deposit. Creation requires a network fee. Shares are minted only when BNB is deposited. BNB and the share token both use 18 decimals, so one full share corresponds to one BNB.
The reserve has no administrator, upgrade mechanism, management fee, pause switch, arbitrary execution, or issuer withdrawal right. The creator field records who deployed it and grants no special control over funds. These constraints do not eliminate smart contract or network risk.
10.1 Deposit, transfer, and redeem
Deposit through the contract’s deposit function to receive shares in the connected wallet. A deposit mints exactly the number of minimum share units corresponding to the wei sent. It does not purchase any BSC tokens.
Shares can be transferred using standard ERC-20 transfers and approvals. The holder can redeem by burning their own shares and receiving the corresponding BNB. No account can redeem another holder’s shares merely because it published or created the token.
Redemption sends BNB back to the calling wallet. If the receiver rejects BNB, the transaction reverts, including the share burn. A reverted transaction may still consume a network fee. Ordinary direct BNB transfers are rejected; use the deposit function.
10.2 Surplus BNB
Some blockchain mechanisms can force BNB into a contract without minting shares. The amount above the BNB corresponding to issued shares is displayed separately as surplus.
Surplus does not increase the minting or redemption rate and cannot be withdrawn by an administrator or distributed to holders. Sending extra BNB does not create a claim to more shares or a dividend. Such funds may be permanently inaccessible.
10.3 A separate future multi-asset design
A reserve that actually holds BSC tokens would need different accounting, valuation, share rights, fees, and exit mechanics. It would require a new contract and a separate user decision. Updating the website cannot turn existing BNB reserve shares into asset exposure.
Proportional in-kind redemption would have to use actual asset balances, account for cash and liabilities, and handle rounding and failed transfers. Target research weights would not establish what assets are available for redemption.
ERC-4626 describes vaults with a single underlying ERC-20 asset. The current native BNB reserve token does not claim ERC-4626 compatibility. Any future design needs its own interface and security review. ERC-4626, OpenZeppelin vault guidance
11 · Quotes, transactions, and verification
Ghesis provides separate paths for BNB reserve operations and BSC token trading. Stock-containing trades use the dedicated PancakeSwap V3 router; crypto-only trades use Uniswap V3 SwapRouter02. Both run on BNB Smart Chain mainnet, chain ID 56. Purchases deliver tokens directly to the quoted wallet. Sales exchange tokens for WBNB and unwrap it to native BNB in the same transaction.
A research budget is a calculation from target weights. A trading quote is a time-limited estimate from onchain liquidity. A reserve balance is a reading at a specific block. These values have different meanings and should not be treated as interchangeable.
11.1 Verifying token creation
The publisher chooses a network, deploying wallet, name, and symbol. Names support 1–64 UTF-8 bytes without control characters. Symbols use 2–12 uppercase letters or numbers and start with a letter. The contract parameters come from the fixed publication.
After wallet confirmation, Ghesis checks the transaction sender, network, zero initial deposit, creation data, receipt, contract address, runtime code, and stored configuration. At least two block confirmations are required, and the receipt’s block must remain on the canonical chain.
Only a matching deployment is associated with the publication as verified. A submitted hash or an address alone is insufficient. Confirmations reduce some uncertainty but do not guarantee irreversible finality or independently audited safety.
11.2 Reserve balances and recovery
Deposit and redemption previews use the fixed BNB exchange rate. Network fees are estimated separately, and balances are read again after confirmation. A wallet rejection, pending transaction, reverted transaction, and confirmed transaction are distinct outcomes.
Reserve readings include the block number, BNB balance, share supply, surplus, and optionally the selected wallet’s balances. If reserve BNB is below the issued share amount, normal previews are suspended while the network and contract data are checked.
If a transaction result is uncertain, recover the original hash before sending again. Repeating a deposit can send funds twice, and repeating creation can deploy another independent contract. An unavailable status is not evidence that nothing was broadcast.
11.3 Reference prices and available routes
Stock references are USD per underlying share; crypto references are USDT per underlying asset unit. Missing, halted, stale or invalid references stop new quotes. Asset identity and reference currency are rechecked before sending. These informational prices do not establish token NAV or onchain fair value.
At a fixed block, route selection compares direct WBNB pairs and two-step routes through USDT. PancakeSwap V3 fees are 0.01%, 0.05%, 0.25%, and 1%; Uniswap V3 fees are 0.01%, 0.05%, 0.3%, and 1%. The greatest valid expected output within the selected venue wins. This is limited AMM routing, not market-wide aggregation or PancakeSwap X / Ondo RFQ integration. PancakeSwap deployments, Uniswap deployments.
Routes with no liquidity, failed quotes, excessive estimated gas, or more than 5% impact relative to the pool price are excluded. Pool price impact does not establish fair value relative to the underlying asset. If any portfolio asset has no valid route, the whole purchase is stopped without silently removing that asset.
Some stock pools have very little active liquidity. A small amount may quote while a larger amount cannot. Coverage is limited to the verified catalog and available routes; an issuer listing alone is not proof that a token can be bought at the requested size.
11.4 Portfolio purchases and approvals
A portfolio purchase divides the entered BNB by integer weights, assigning any rounding remainder to the last holding. Every leg has its own minimum output. All swaps run in one router transaction, so failure of one leg reverts the whole purchase. Network fees may still be charged.
Quotes remain valid for 90 seconds, with an onchain deadline 180 seconds after quote creation. The interface offers slippage settings from 0.25% to 3%. Before sending, Ghesis rechecks the wallet, network, prices, and balances, and checks the complete transaction. Prices can still move before execution.
Selling supports one BSC token at a time. Ghesis requests approval only for the entered amount to the fixed router selected by the quote. Check the final allowance in your wallet. Approval is a separate transaction; after it confirms, a valid quote and another wallet confirmation are needed to sell.
Purchase and sale recipients are fixed to the quoted wallet. The trading interface does not accept an arbitrary recipient or router. Buying with native BNB does not require a BSC token approval.
11.5 Pending transactions and received assets
A quote is reserved before the wallet opens, preventing duplicate sends from competing pages. A wallet with an unresolved trade must recover or verify that trade before creating another quote. If broadcast status is unknown, sending remains paused until the original transaction is found or the user confirms that nothing was broadcast.
Verification compares the transaction’s account, router, BNB amount, and call data with the saved quote. After at least two confirmations, it checks receipt events and net asset movements. Purchases must deliver the expected tokens above each minimum; sales must debit the exact input and unwrap sufficient BNB.
A sped-up or canceled transaction must match the original sender and nonce. A confirmed replacement updates the record. Failed or canceled trades require a fresh quote. Network delays can leave a broadcast transaction temporarily invisible, so absence from a data provider is not a reason to send again.
Trading currently supports standard EOA wallets without contract code. Contract wallets and EIP-7702 delegated accounts are not supported by the current received-asset verification flow.
12 · Identity and control
A site account determines who can publish and manage a publication. The contract creator is the wallet that sent the creation transaction. Share ownership follows onchain balances. These are separate identities: signing in does not give access to another wallet’s shares, and being the creator does not grant reserve withdrawal powers.
Publication does not require an additional wallet message signature. A published thesis should therefore not be described as wallet-signed research. Content hashes identify versions; they do not prove real-world authorship, investment quality, or contract safety.
The reserve’s fixed configuration cannot be edited after deployment. There is no administrator to change names, weights, the BNB rate, or the publication reference; mint unbacked shares; withdraw surplus; or redeem for someone else.
This also limits recovery. Incorrect metadata cannot be repaired in the same contract, lost keys cannot be restored by an administrator, and the implementation cannot be upgraded. A new contract requires a separate decision by the user.
The website, publication service, and blockchain data providers remain dependencies. Site access controls do not add access restrictions to a public blockchain contract. Anyone with its address can interact according to its onchain rules.
| Role | Control | Limit |
|---|---|---|
| Publisher | Publishes research and prepares its token | Does not own another user’s shares |
| Creator | Deploys the contract | Has no administrative or withdrawal privilege |
| Share holder | Transfers or redeems their own shares | Cannot withdraw surplus or change the configuration |
| Ghesis service | Stores publications and verifies associated transactions | Cannot sign wallet transactions |
| Wallet owner | Approves and sends transactions | Must review the network, amount, and recipient |
13 · Costs and fees
The current BNB reserve contract charges no deposit, redemption, management, or creator fee. Deposited wei and minimum share units exchange 1:1. The creator does not receive automatic shares as the reserve grows and cannot withdraw surplus as revenue.
Users pay network fees for creation, deposits, redemptions, approvals, and transfers. A zero initial BNB deposit does not mean a contract creation transaction has no cost. Review the final network fee in your wallet.
BSC token trading includes AMM pool fees, bid–ask differences, slippage, and network fees. A token approval before selling may require an additional network fee. Ghesis currently adds no separate trading service fee. Pool fees are reflected in the quoted output.
A fixed BNB redemption rate does not preserve a fixed dollar value. BNB price movements and transaction costs affect the value a user measures in other currencies.
Any future fees would need clear terms describing their basis, timing, recipient, and effect on proceeds. They cannot be added to an existing non-upgradeable reserve contract merely by changing the website. Reserve shares do not include a promise of a platform token, airdrop, or business revenue.
14 · Risks and limitations
Stocks, ETFs, stock tokens, crypto tokens and pegged assets can lose value. A theme or portfolio weight is a research choice, not evidence of returns or diversification. Multiple holdings may share market, bridge, issuer and protocol risk.
Trading depends on BSC token contracts, PancakeSwap V3, Uniswap V3, WBNB, USDT, the wallet and data providers. Code checks do not guarantee third-party safety. Stablecoins and pegged assets can lose their peg.
Pool price impact does not establish fair value or rule out manipulation. The app does not have an independent manipulation-resistant price oracle. Reference markets, token contracts and liquidity can change or become unavailable.
All transactions use mainnet BNB. Local tests and mainnet forks do not constitute a contract audit. Two confirmations do not guarantee finality. Reverted transactions can still consume fees.
| Situation | Product response | Remaining risk |
|---|---|---|
| Browser storage unavailable | Keep the editor available and offer export | Unsaved browser data may be lost |
| Wallet rejected the request | Do not mark the transaction complete | The user must still check wallet activity |
| Pending or unavailable transaction status | Preserve the record and recover the original hash | Sending again can duplicate an operation |
| Contract or transaction mismatch | Do not mark the operation verified | A similarly named third-party token may still mislead |
| Redemption receiver rejects BNB | Revert the transaction and share burn | Network fees may still apply |
| Extra BNB reaches the reserve | Show it separately as surplus | It cannot be redeemed or withdrawn |
| No valid route for a holding | Stop the whole portfolio purchase | Liquidity and prices may remain unavailable |
| Lost wallet key or contract defect | No administrator recovery or upgrade | Losses can be irreversible |
15 · What comes next
Ghesis currently supports AI and curated research, editable allocations, concentration analysis, browser revisions, exports, fixed publications, BNB reserve token creation and redemption, and stock-token trading through PancakeSwap V3 and crypto trading through Uniswap V3.
Research improvements may include broader theme coverage, refreshed catalogs, clearer version histories, and source-linked information retrieval. Research quality and investment performance need separate evaluation. AI research does not require authority over funds.
Operational priorities include reliable transaction recovery, consistent asset and balance verification, and independent security review. An unfinished review will not be presented as completed.
Multi-asset reserves would be a separate protocol with new accounting, valuation, share rights, permissions, fees, and exit mechanics. Existing BNB reserves will not be upgraded into asset funds or have their balances moved automatically.
Multi-asset-backed fund shares, automatic rebalancing, NAV accounting, issuer primary-market minting and redemption, and V4 or UniswapX aggregation are not currently available. Future directions are not delivery-date or performance commitments.
| Area | Current experience | Potential extension |
|---|---|---|
| Research | AI and curated portfolios | Broader coverage and source-linked research |
| Publishing | Fixed versions and content hashes | More tools for comparing research versions |
| BNB reserves | Independent contracts with fixed redemption | Continued verification and independent review |
| Trading | V3 BSC token purchases and sales | Broader route and market coverage |
| Multi-asset shares | Not available | A new protocol with separate terms and review |
Stock research, BSC trading, and BNB shares
Source-linked research and broader market coverage
Independent review and a separate protocol design
16 · Terms and sources
Networks: BNB Smart Chain documentation. Asset identities: PancakeSwap token list. Catalog membership is not endorsement. Stock identities: Ondo, xStocks.
Underlying reference prices: Binance Spot market data. USDT reference prices are distinct from BSC execution quotes. Stock references: Robinhood public stock API, denominated per underlying share rather than per BSC token.
Reserve implementation: Solidity 0.8.30 and OpenZeppelin ERC20 with ReentrancyGuard. Download the source and complete compiler input from the contract section. The contract has no owner withdrawal or upgrade authority.
Trading: Uniswap BSC deployments and SwapRouter02 source. Available routes are a subset of the broader market. Stock trades: PancakeSwap V3 router source and deployments.
| Term | Meaning in Ghesis |
|---|---|
| Investment thesis | A written view about a change and its effects |
| Research portfolio | An editable list of assets, target weights, and reasoning |
| Basis point (bp) | One hundredth of a percent; 100 bp = 1% |
| Catalog snapshot | Asset identities and addresses captured at a stated time |
| Publication | A fixed research version preserved under a site account |
| Content hash | A fingerprint of research content and asset references |
| Publication hash | A reference binding a publication identity to its content hash |
| Creator | The deploying wallet, recorded without administrative privilege |
| Reserve share | An 18-decimal ERC-20 unit with fixed BNB redemption |
| Surplus | BNB above the issued share amount, without a withdrawal right |
| Pegged token | A representation of another asset with separate issuer, bridge or custody dependencies |
| NAV | Assets minus liabilities at a stated valuation time; not used for fixed BNB redemption |
| Quote | A time-limited estimate of an onchain swap |
| Receipt | Evidence of transaction execution; finite confirmations are not absolute finality |