DOWNLOAD RESEARCH
Your download.
Your choice to share.
We are exploring optional peer-assisted delivery: people could help other eligible users download an authorized game or asset.
Not available in the public app. Seeding is being tested in a private, same-computer experiment. Paid purchases remain closed.
How the planned desktop flow works
Review purchase and license terms.
Before a paid download, review the item’s price, compatibility, license, delivery and refund information. Accept the applicable terms explicitly. Any consent required for immediate digital delivery must be separate from optional seeding.
Download your item.
Under the proposed flow, an accepted purchase would immediately start the download. The complete file and installation would be verified before offering seeding. A purchase, download or installation must never turn seeding on.
Choose seeding separately.
Only after verified installation, you could opt in for an eligible item. Seeding would start off. Declining it must not remove your owned access.
This page does not take payment, accept terms or start a transfer. There is no browser checkout.
Availability and failed deliveries
In the proposed store, an item with no active, verified seed would be hidden from new shoppers. Existing owners would keep its library entry and license. A peer appearing online cannot guarantee that a download will complete.
An accepted purchase would reserve coins and immediately start the download. Seller settlement would wait for complete, verified delivery. If delivery fails within bounded attempts, the reservation would be released or the coins returned automatically. A card refund, when required, follows the payment provider’s process and is not necessarily immediate.
These availability, reservation and recovery rules are proposed safeguards, not a live payment or delivery service. Mandatory remedies for undelivered, faulty or misdescribed content remain separate from voluntary seeding. Automatic coin recovery does not replace a legally required refund through another payment method.
WHAT SHARING MEANS
A choice with clear limits.
Seeding sends file chunks to another downloader. Owning a copy does not grant redistribution rights: only an exact release explicitly authorized by its publisher could be eligible.
Planned in-app and in-engine sharing would keep the original listing, publisher and exact version. A buyer who seeds would not create a new listing or gain ownership of another creator’s work. More eligible peers could improve availability; peer count is not a quality rating.
Direct peers may see your IP address or other network identifiers. Encryption is not anonymity. Uploads can use bandwidth, mobile data, CPU time, power and battery.
- Off by default, with a separate choice for each eligible item.
- Visible upload-rate, data-budget and connection limits before starting.
- Pause or stop future uploads without losing your owned copy.
- Stopping cannot recall bytes already delivered to another device.
- No promise of faster downloads, zero operating cost or invisible resource use.
PLANNED APP LOCATIONS
Beside your downloads.
My Library → item → Optional seeding would hold the item-specific choice and activity. Settings → Downloads & sharing would hold global limits and a stop-all control. These menus are proposed, not available controls.
Separate from editor work.
Opening ASHVEIL ENGINE, editing an asset or saving a project must not enroll a file for sharing. A publisher’s approved release is separate from your working files.
Unavailable peers must be reported honestly. A seller going offline does not erase delivery or refund obligations.
EVIDENCE & LIMITS
What has been tested?
The private lab transferred a small original test asset between two peers in one browser page. Pause, disconnect, resume, complete-file hash verification and saving the verified copy were tested.
This does not validate transfers between separate computers, internet availability, large bundles, paid delivery or production security. Public seeding is unavailable today.
A matching hash proves byte integrity, not ownership, license permission or asset quality. Final purchase terms, privacy disclosures and delivery safeguards still need review before launch.