Cardano Developers |
Cardano Developers Home |
Select language |
Select theme |
Last updated |
Report a documentation issue |
Search |
Previous |
Next |
Search Cardano Developers |
Perform search |
Open search bar |
Close search bar |
Main |
Close main navigation menu |
Open main navigation menu |
Cardano Developers Logo |
| saturation |
select_a_calculator |
i_want_to |
delegate_my_stake |
run_a_stake_pool |
show_advanced_options |
ada_label |
ada_descriptor |
ada_label_operator |
ada_descriptor_operator |
treasury_rate_label |
treasury_rate_descriptor |
expansion_rate_label |
expansion_rate_descriptor |
reset |
share |
tweet |
copy_to_clipboard |
currency_label |
currency_descriptor |
exchange_rate_label |
exchange_rate_descriptor |
fixed_fee_label |
fixed_fee_descriptor_ada |
fixed_fee_descriptor |
stake_pool_control_label |
stake_pool_control_descriptor |
total_stake_pools_label |
participation_rate_label |
participation_rate_descriptor |
operators_stake_label |
operators_stake_descriptor |
stake_pool_margin_label |
stake_pool_margin_descriptor |
stake_pool_performance_label |
stake_pool_performance_descriptor |
delegation_rewards |
yearly |
yield |
private_stake_pool_label |
private_stake_pool_descriptor |
running_costs |
stake_pool_operation_rewards |
combined_rewards |
transaction_fees_per_epoch_label |
transaction_fees_per_epoch_descriptor |
influence_factor_label |
influence_factor_descriptor |
Pool saturation |
Select a calculator |
I want to |
Delegate my stake |
Run a stake pool |
Advanced options |
Ada amount |
Set the amount of ada you want to delegate |
Pledge amount |
Set the amount of ada you want to pledge to your pool |
Treasury rate |
% of gross rewards distributed to the treasury |
Expansion rate |
% of reserves released per epoch |
Reset |
Share |
Tweet |
Copy to clipboard |
Currency |
Please select the currency you wish to see results in |
Exchange rate |
|
Stake pool daily fixed fee |
Set the fixed fee covering daily stake pool running costs
|
Set the fixed fee covering daily stake pool running costs, in ADA ({{amount}} ADA)
|
Stake pool total stake |
Set the amount of stake the pool controls, as a percentage of the total available stake |
Total stake pools |
Delegation participation rate |
Set the total amount of stake delegated across the network in this epoch, as a percentage of the total available stake |
Stake pool operator's stake |
Set the size of the stake pool operator's stake |
Stake pool operator reward percentage |
Set the amount of rewards taken by the stake pool operator, as a percentage of the total rewards earned by the pool |
Stake pool performance |
How efficient is the stake pool, influences the stake pools penalty on the gross rewards. Any penalties go to the treasury |
Delegation rewards |
Yearly |
Yield |
Private stake pool |
Is the stake pool open to third party staking |
Running costs |
Stake pool operation rewards |
Combined rewards |
Average transaction fees per epoch |
The average amount of transaction fees per epoch are added to the net distribution of rewards and used to calculate the distribution rate from the reserves |
Influence factor (a0) |
System parameter used to control the ADA distribution rate |
|
The KEVM is a high quality, formally verified smart contract virtual machine compatible with the Ethereum virtual machine (EVM). Formally specified in the K framework, the KEVM uses formal semantics for elements such as the configuration and transition rules of EVM, resulting in a more secure virtual machine for smart contracts.
|
The IELE testnet underpins the path to a more secure, robust smart contract design for Cardano. It is a new register-based virtual machine for smart contracts built to take account of the lessons learned from LLVM. IELE aims to provide the most secure and high-performance platform for running smart contracts, while also delivering the most flexible set of interfaces possible to execute different programming languages.
|
| funds |
invalid_address |
server_error |
endpoint_not_found |
too_many_attempts |
too_many_attempts_retry |
address_helper_text |
api_key_helper_text |
request_funds |
request_more_funds |
success_heading |
verify_transaction_hash |
transaction_successful |
please_complete_recaptcha |
funds |
Invalid address |
Server error |
Server endpoint not found |
Too many requests |
Too many requests, retry after {{ time }} |
The address to send funds to |
Optional API key to bypass rate limiting |
Request funds |
Request more funds |
Success |
Please verify the following transaction hash: |
Your transaction has been successful and __{{ amount }}__ have been sent to __{{ address }}__. |
Please complete the ReCAPTCHA |
|
| version |
sha_checksum |
verify_signature |
pgp_signature |
verify_checksum |
copy_to_clipboard |
error_fetching_data |
no_releases_available |
platforms_order |
windows |
darwin |
linux |
Version |
SHA256 checksum |
Verify signature |
PGP signature |
Verify checksum |
Copy to clipboard |
Error fetching data |
No releases are currently available right now, please check back later. |
|
| short_label |
full_label |
checksum_instructions |
signature_instructions |
Windows |
Windows 8.1 and 10, 64 bit |
## Windows checksum verification instructions
### Installer integrity
SHA256 checksum can be verified using the following command:
```shell
certutil -hashfile C:\Users\YOUR_USERNAME\Downloads\{{ filename }} SHA256
```
Instead of typing the path to the Daedalus installer executable use drag and drop:
1. Press Windows Start Menu
1. Type cmd
1. You should see cmd.exe in the list of results. Click on cmd.exe to launch it.
1. Type or paste: certutil -hashfile
1. Press space
1. Drag and drop Daedalus installer from Explorer to Command Prompt
1. Press space
1. Type or paste: SHA256
1. Press enter key
You should see the following output, where string on the second line is the SHA256 checksum:
```shell
SHA256 hash of file C:\Users\YOUR_USERNAME\Downloads\{{ filename }}:
{{ sha256 }}
CertUtil: -hashfile command completed successfully.
```
|
## Windows PGP signature verification instructions
1. Obtain both the Daedalus installer .exe file, and its corresponding .exe.asc signature file -- put them in the same directory.
1. Obtain the GNUPG package from [ https://www.gpg4win.org/](https://www.gpg4win.org/)
1. Proceed with installation and launch the Kleopatra component.
1. Unless you already have a personal GPG key, you will have to create one (which is required for step 6):
- Select the menu item File -> New keypair -> Create a personal OpenPGP key pair.
- Enter a name and an email address that suit you personally.
- Choose a passphrase to protect your personal key (NOTE: the passphrase can be empty, but it is not recommended if you intend to use GNUPG in future).
1. Import the IOHK key:
- File -> Lookup on Server
- Allow network access to 'dirmngr', if the prompt arises
- Search for signing.authority@iohk.io
- Import the key
- Do not certify the key just yet
- Right-click on the key, and choose "Details"
- Ensure that the fingerprint is D32587D4090FE461CAEE0FF4966E5CB9CBFAA9BA
- If it's not, the wrong key was imported, right click and delete
- If it is, we are good to go
1. Certify the IOHK key (this designates trust and is required for the next step):
- Once you have a personal GPG key, right-click on the imported IOHK key and choose Certify
- Enable the IOHK user ID
- Tick the I have verified the fingerprint checkbox (since you did, as per step 5), and proceed.
- You should receive a message saying Certification successful
1. Verify the installer binary:
- Click the Decrypt/Verify button on the Kleopatra toolbar
- Choose the Daedalus installer .exe file in the file dialog (the .asc signature file must reside in the same directory)
1. If the verification is successful, you will receive a green-tinted message box saying:
- Valid signature by signing.authority@iohk.io
- Date of signature
- With certificate D325 87D4 090F E461 CAEE 0FF4 966E 5CB9 CBFA A9BA
- Anything else would constitute a signature verification failure.
|
|
| short_label |
full_label |
checksum_instructions |
signature_instructions |
Mac OS |
Mac OS 64 bit |
## MacOS checksum verification instructions
### Installer integrity
SHA256 checksum can be verified using the following command:
```shell
shasum -a 256 ~/Downloads/{{ filename }}
```
Instead of typing the path to the Daedalus installer executable use drag and drop:
1. Open Terminal
1. Type or paste: `shasum -a 256`
1. Press space key
1. Drag and drop Daedalus installer from Finder to Terminal
1. Press enter key
You should see the following output, where string before the file path is the SHA256 checksum:
```shell
{{ sha256 }} ~/Downloads/{{ filename }}
```
|
## MacOS PGP signature verification instructions
1. Obtain both the Daedalus installer .pkg file, and its corresponding .pkg.asc signature file -- put them in the same directory.
1. If you already have the GPG Suite installed, and a personal key generated, please skip to step 5, and if not, proceed with the next step.
1. Go to [ https://gpgtools.org](https://gpgtools.org), head to the GPG Suite section, download the .dmg file and install it:
* Right-click the .dmg file, then Open, which will open a new window with two icons: Install and Uninstall
* Right-click the Install icon, and choose Open with.. -> Installer, which should start the GPG Suite installer
* Follow through the installation wizard
1. Once GPG Suite installation completes, it will ask you to create a new key pair (this is required for step 6, so please don’t skip it):
* Enter a name and an email that suit you personally.
* Choose a passphrase to protect your personal key (NOTE: the passphrase can be empty, but it is not recommended if you intend to use this key and GPG Suite in future).
1. Import the IOHK key using the GPG Keychain application:
* Select Key -> Lookup Key on Key Server in the application menu
* Search for signing.authority@iohk.io
* Choose the key with fingerprint CBFAA9BA with the user ID “IOHK Signing Authority ”, then click Retrieve Key
* Verify (right-click the imported key, then Details) that the fingerprint of the imported key is D325 87D4 090F E461 CAEE 0FF4 966E 5CB9 CBFA A9BA
* If it's not, the wrong key was imported, right click and delete
* If it is, we are good to proceed with the next step.
1. Sign the imported IOHK key (this designates trust and is required for the next step):
* Right-click on the imported IOHK key, then “Sign”.
1. Verify the installer binary:
* Right-click the Daedalus installer (.pkg file) in Finder (do NOT right click on the .asc file, that will not work), then select Services -> OpenPGP: Verify Signature of File (the .asc signature file must reside in the same directory)
* The Verification Results dialog will then appear with the verdict in the Result column:
1. “Signed by: IOHK Signing Authority 1471941A -- full trust” -- if successful
1. ..anything else means there was no valid signature for the installer.
|
|
| short_label |
full_label |
checksum_instructions |
signature_instructions |
Linux |
Linux 64 bit |
## Linux checksum verification instructions
### Installer integrity
Verify the sha256 hash:
```shell
sha256sum ~/Downloads/{{ filename }}
```
Expected:
```shell
{{ sha256 }}
```
|
## Linux PGP signature verification instructions
- Obtain both the Daedalus installer .bin file, and its corresponding .bin.asc signature file -- put them in the same directory.
- Ensure that the gpg2 command is available (assuming Ubuntu Linux) in your shell, and if not -- execute the following shell command (shell commands further indicated by this bold monospace font):
- `apt-get install gnupg2`
- Unless you already have a personal GPG key, create one (this is required for step 5):
- `gpg2 --generate-key`
- Supply an user ID (real name and email) that suit you personally
- Choose a passphrase to protect your personal key (NOTE: the passphrase can be empty, but it is not recommended if you intend to use this key and GNUPG in future)
- Import the IOHK key:
- `gpg2 --keyserver hkp://pool.sks-keyservers.net --search-keys signing.authority@iohk.io`
- In the selection dialogue, choose the key with fingerprint 966E5CB9CBFAA9BA
- Sign the IOHK key (this designates trust and is required for the next step):
- `gpg2 --lsign D32587D4090FE461CAEE0FF4966E5CB9CBFAA9BA`
- Verify the installer binary using the .asc signature (the .asc signature file must reside in the same directory as the installer binary):
- `gpg2 --verify {{ filename }}.asc`
- Successful verification should produce a message like follows:
```shell
gpg: assuming signed data in {{ filename }}.pkggpg: Signature made ...DATE...gpg: using RSA key 9F9840B50AE539A2732CF646C131557F1471941Agpg: checking the trustdbgpg: marginals needed: 3 completes needed: 1 trust model: pgpgpg: depth: 0 valid: 1 signed: 1 trust: 0-, 0q, 0n, 0m, 0f, 1ugpg: depth: 1 valid: 1 signed: 0 trust: 1-, 0q, 0n, 0m, 0f, 0ugpg: next trustdb check due at ...DATE...gpg: Good signature from IOHK Signing Authority <signing.authority@iohk.io>
```
|
|
|