SOLANA TOOLS / LICENSE
Clear rights. Defined delivery.
Commercial work is quoted individually. The signed agreement defines the deliverables and rights; this page explains the proposed licensing model.
White-label deployment
Branding and deployment are specified per engagement. A white-label deployment alone does not grant unrestricted source redistribution or rights to third-party brands.
Perpetual enterprise source license
The proposed source license is non-exclusive. Authorized commercial use and modification cover the project-owned code and deployment scope listed in the agreement.
Exclusive rights by separate agreement
Exclusivity, copyright assignment, sublicensing, resale and multi-client deployments require explicit written terms. Perpetual use does not imply perpetual maintenance.
Technical and licensing questions
Can we modify the Pump.fun and Raydium integrations?
The enterprise source agreement can authorize secondary development of project-owned Pump.fun and Raydium adapter code for the licensed commercial product. Deployment count, affiliated-company use and redistribution limits must be specified. Third-party SDK, protocol-service and brand terms remain applicable.
What is delivered with white-label deployment versus source licensing?
White-label delivery covers the agreed branding, domain and deployment. Enterprise source delivery adds the named code, build documentation and agreed modification rights. Protocol modules, acceptance checks and support duration are listed in the contract.
Does the Raydium LP manager support every pool and Token2022 asset?
Coverage depends on pool type, operation and token extensions. Define creation, liquidity, position and fee-collection acceptance separately for each supported pool type. Code coverage is not a substitute for real-wallet acceptance with your intended assets.
Can we use our own RPC and run an unattended trading bot?
The current static frontend supports configurable browser-compatible RPC endpoints and connected-wallet signing. Private API proxies, server-side signing, unattended strategies and dedicated RPC scheduling are separately scoped work. Secret credentials must not be embedded in public frontend configuration.
How are delivery acceptance and protocol upgrades handled?
Bind acceptance to a code version and agreed protocol actions. Verify build and deployment, wallet signing, on-chain results and uncertain-confirmation recovery, retaining agreed small-value transaction records. Ongoing protocol adaptation, service fees and response times require separate maintenance terms.
Review your deployment with 0xF1
Share your target workflows, pool types, branding requirements and source-license needs. Use the contact options on fone.cc to request a technical walkthrough and a scoped quote.
Contact details and availability are maintained on the creator’s website.