Build ownership into everyday activity.
This documentation describes the Stockfolk product model, intended system architecture, user flows and production considerations.
Getting started
Stockfolk is designed around a simple sequence: connect an account and wallet, select a portfolio allocation, generate eligible reward value, and claim supported assets onchain.
- Connect. Link a compatible wallet and create your Stockfolk profile.
- Allocate. Choose how supported assets should be weighted.
- Earn. Eligible partner activity can generate reward value.
- Review. See pending rewards and the assets they map to.
- Claim. Settle supported assets to your wallet when the production claim flow is enabled.
How it works
The product separates user activity from asset settlement. Reward events enter a ledger first. Portfolio rules determine allocation. Settlement happens only after the user initiates a claim.
Architecture
A production deployment should keep the browser or client surface lightweight and move sensitive calculations, partner verification and settlement orchestration into auditable services.
Public client code should never contain private keys or privileged settlement credentials.
Tokenized stocks
“Tokenized stock” is an umbrella term. The rights attached to a token depend on the issuer, structure and jurisdiction. A production Stockfolk deployment should disclose the exact asset issuer, contract address, pricing source, redemption or custody model, and legal rights for each supported market.
Portfolio system
Users can set an allocation across supported assets. New reward value is assigned according to the active allocation at the time the reward is finalized. Changes should apply prospectively and be recorded in the user activity history.
Stockfolk should provide controls and information, not personalized investment recommendations.
Security
Production architecture should use wallet signatures for user authorization, server-side verification for reward events, rate limits, replay protection, audit logs, contract allowlists and monitored settlement queues.
Stockfolk should never request or store user seed phrases or private keys.
Risk
Tokenized assets can lose value and may involve market, liquidity, issuer, counterparty, bridge, custody and smart-contract risk. Availability and legal treatment may differ by jurisdiction.
Privacy
A production browser integration should minimize collection, process only data necessary for reward attribution, and publish a clear data-retention policy. Sensitive browsing content should not be collected merely because an extension can access it.
FAQ
Where do rewards come from?
Reward value can be funded by eligible commercial activity such as partner or affiliate economics. Production sources should be disclosed clearly.
Can I change my allocation?
Yes. The interface is designed to let users update portfolio weights for future reward allocation.
Can stock prices fall?
Yes. Any market-linked asset can move up or down.
Does Stockfolk control my wallet?
The intended model is non-custodial user authorization. Production behavior should be verified against deployed contracts.
Is Stockfolk investment advice?
No. The product should provide information and user controls, not personalized investment recommendations.
Roadmap
Core website, dashboard, portfolio and documentation.
Supported-wallet connection and account authorization.
Verified event ingestion and transparent reward accounting.
Asset allowlists, claim routing and production monitoring.