New Solana Setup Project
This template allows you to sell your software directly without having to rely on entities such as banks or credit card companies, leveraging the decentralized cryptocurrency and its integrated recordkeeping.
The fields and settings below are saved in your new setup project, primarily in the call made to the SOL Transaction plug-in. You may freely revise any of these settings after your project has been created.
Connection
The first step in processing decentralized cryptocurrency transactions is connecting to the .
mainnet: Use real money. For production deployments.
Transactions will be performed using real cryptocurrency.
For production use, ensure to select this option.
testnet: Use testing money. Less stable and more bleeding edge than devnet.
Transactions will be performed using freely obtained (and worthless) testing cryptocurrency on the .
Select this option during testing and development only. Please note that the is known to have more prolonged downtime than the devnet, your second testing alternative.
devnet: Use testing money. For testing and development scenarios.
Transactions will be performed using freely obtained (and worthless) testing cryptocurrency on the .
Select this option during testing and development only.
Solana Faucet
As of this writing, you may obtain free testing currency from the located at https://faucet.solana.com/ for both the and the.
Product
The next step is to define your product and price.
Suggestions on how to generate your product code
To automatically generate a code, select one of the options available in this drop-down list.
Unique Code
You may type in any unique identifier in this field.
Any variables entered in this field will be resolved at runtime.
Price (in USD)
Type the price of your product in this field.
Do not use any currency symbols or thousand separators.
You may use a period (.) as a decimal separator.
Payment
The last step is entering your payment address, and choosing your licensing model (arising out of how you choose to record your customers's machines on the ).
Charge for each new installation, even if on the same PC
Your setup script will use the Generate GUID command to create a brand-new unique identifier each time setup is run.
Therefore, since each installation would be recorded under a newly generated unique identifier in the , any reinstallations without making a new payment become impossible.
However, if setup is cancelled or fails for any reason, any rendered payment would not be forfeit - the unique identifier would be saved using the Set Variable command's Set Persistent Variable mode.
Charge for each unique Windows instance, even on the same PC
Your setup script will use the Get System Settings command with the Pseudo Unique Machine Identifier parameter to identify each machine based on a registry key created during the first time installation of the operating system.
Since this identifier may not always change after an operating system image has been cloned to different hardware, your software could be reinstalled on a potentially unlimited number of cloned machines with this approach, after having been purchased only once on a clone (or original image).
However, when the operating system is manually reinstalled, this identifier would change - therefore requiring new payments, even if the underlying hardware (and operating system version) did not change at all.
Charge for each unique hardware and operating system combination
Your setup script will use the Generate System ID command to generate a unique hash identifying the current hardware and operating system setup is running on.
Since this hash is immutable as long as the underlying equipment remains unchanged, reinstallations would be permitted in the same exact environment without limitation.
However, upgrading the operating system, or changes to the underlying hardware, would require making a new payment before permitting an installation; as the new hash would not have yet been saved in the .
Charge any customer only once, allowing installations anywhere
Your setup script will use the hard-coded string literal UNLIMITED to record installations in the , thus permitting unlimited installations everywhere with a single purchase.
Different users would still need to purchase their own copy of the product, but once purchased, the product would be available to them everywhere.
Your Public Key
Type in your wallet public key here.
Ensure you update this field - the default value here is only an example, and would forfeit all of your revenue!
As of this writing, you may easily create your wallet using third party services such as Phantom.
Please note that any services you may receive from third parties are subject to their terms entirely.



