Use the account_balance rather than the legacy account_balance_dfx on the ICP ledger.
Extend dfx ledger transfer and dfx ledger balance to support ICRC-1 standard.
As announced dfx start now runs PocketIC by default.
Running a local replica is still possible with --replica, but this option will be removed in the near future.
dfx will now record information about each dfx command executed, and periodically send this information to a DFINITY server, by default.
For more information or to comment, please see https://forum.dfinity.org/t/dfx-telemetry-proposal-2025/41569.
You can see what data dfx collects by inspecting the file at dfx info telemetry-log-path.
You can disable this entirely with dfx config telemetry off or configure it to only collect
locally with dfx config telemetry local.
Displays the path of the telemetry log file.
fix: Warning and error messages now correctly suggest dfx info security-policy when suboptimal security policies get used
Updated the canister creation fee to 500B cycles as documented.
Improve the ouput of dfx build with the canister names that were built, example as below.
$ dfx build
Building canister 'hello_backend'.
Building canister 'hello_frontend'.
Finished building canisters.
Implement dfx ledger approve and dfx ledger transfer-from subcommands that comply with the ICRC-2 standard.
Implement dfx ledger allowance subcommand that complies with the ICRC-2 standard.
- Add VetKD types and methods to management canister IDL
- The VetKD test key id
Bls12_381_G2:dfx_test_keyis now enabled when startingdfxwith--replica.
Updated Motoko to 0.14.4
Updated replica to elected commit f6f5e0927d14886e4bd67f776ee889f31cec2364. This incorporates the following executed proposals:
fix: dfx canister install and dfx deploy with --no-asset-upgrade no longer hang indefinitely when wasm is not up to date
Updated Motoko to 0.14.2
- Module hash: 865eb25df5a6d857147e078bb33c727797957247f7af2635846d65c5397b36a6
- #4095
Updated replica to non-elected commit ebb190bf1da0dba3e486b78c95cf5a3c5542e2f3.
This includes X_OC_JWT and X_OC_API_KEY cors headers in PocketIC HTTP gateway (see dfinity/ic#4154).
This also incorporates the following executed proposals up to commit 2f02a660f6f17b5a78c13d9b372f74c8228f79b8:
fix: dfx canister install and dfx deploy with --no-asset-upgrade no longer hang indefinitely when wasm is not up to date
Due to the incompatibility between the APIs on the replica port and the PocketIC port, dfx info replica-port
no longer works with PocketIC, and the PocketIC port is provided by a new command, dfx info pocketic-config-port.
The first of a suite of baseline tests to automate testing starter projects. Makes sure that sveltekit, react, vue, and vanilla frontends are compatible with other dfx or asset canister changes.
DFX's default security headers cause Safari to break when viewing local canisters. Warning messages have been added to the frontend project templates when the page is broken that indicate to try switching browsers.
dfx canister call, dfx canister status, and dfx canister update-settings take
an additional CLI argument --impersonate to specify a principal
on behalf of which requests to a local PocketIC instance are sent.
This adds support for the WASM memory threshold, used in conjunction with --wasm-memory-limit.
When the remaining memory until the limit falls below the threshold, the canister's
on_low_wasm_memory handler is run.
Recently we made dfx deploy include some chunk data in CommitBatch, in order to streamline
deploys for smaller projects. dfx deploy splits up larger change lists and submits them in
smaller batches, in order to remain within message and compute limits.
This change also applied to dfx deploy --by-proposal, which submits all changes in a single
message. This made it more likely that dfx deploy --by-proposal will fail due to exceeding
message limits.
This fix makes it so dfx deploy --by-proposal never includes this chunk data in
ProposeCommitBatch, which will allow for more changes before hitting message limits.
dfx start --pocketic is now compatible with --force and shared networks.
This used to be a warning. A hard error can abort the command so that no insecure state will be on the mainnet.
Users can suppress this error by setting export DFX_WARNING=-mainnet_plaintext_identity.
The warning won't display when executing commands like dfx deploy --playground.
Added a flag --replica to dfx start. This flag currently has no effect.
Once PocketIC becomes the default for dfx start this flag will start the replica instead.
You can use the --replica flag already to write scripts that anticipate that change.
An extension can define one or more project templates for dfx new to use.
These can be new templates or replace the built-in project templates.
This affects the following commands:
dfx canister deletedfx canister deposit-cyclesdfx canister startdfx canister statusdfx canister stopdfx canister uninstall-codedfx canister update-settingsdfx ledger fabricate-cycles
Canisters with Motoko's Enhanced Orthogonal Persistence feature require wasm_memory_persistence = Keep when they get installed.
Previously, when dfx attempted to install canisters with EOP enabled to a playground it didn't set wasm_memory_persistence properly.
If users run dfx deploy without enough cycles, show additional messages to indicate what to do next.
Error explanation:
Insufficient cycles balance to create the canister.
How to resolve the error:
Please top up your cycles balance by converting ICP to cycles like below:
'dfx cycles convert --amount=0.123'.
If users run dfx deploy --playground but the backend is not updated with the latest frontend canister wasm
the error message will explain this properly and recommends asking for help on the forum since this can't be resolved by users.
If users run dfx cycles convert without enough ICP tokens, show additional messages to indicate what to do next.
Error explanation:
Insufficient ICP balance to finish the transfer transaction.
How to resolve the error:
Please top up your ICP balance.
Your account address for receiving ICP from centralized exchanges: 8494c01329531c06254ff45dad87db806ae6ed935ad6a504cdbc00a935db7b49
(run `dfx ledger account-id` to display)
Your principal for ICP wallets and decentralized exchanges: ueuar-wxbnk-bdcsr-dnrh3-rsyq6-ffned-h64ox-vxywi-gzawf-ot4pv-sqe
(run `dfx identity get-principal` to display)
Add pre-install tasks, which can be defined by the new pre-install key for canister objects in dfx.json with a command or list of commands.
Warn when the 'canister_ids.json' file is first generated for persistent networks.
dfx deploy --network ic
...
test_backend canister created on network ic with canister id: j36qm-pqaaa-aaaan-qzqya-cai
WARN: The "/home/sdk/repos/test/canister_ids.json" file has been generated. Please make sure you store it correctly, e.g., submitting it to a GitHub repository.
Building canisters...
...
Provides units for all fields of canister status.
$ dfx canister status pxmfj-jaaaa-aaaan-qmmbq-cai --ic
Canister status call result for pxmfj-jaaaa-aaaan-qmmbq-cai.
Status: Running
Controllers: uom2z-lqsqq-qbn4p-nts4l-2xjfl-oeivu-oso42-4t4jh-54ikd-ewnvi-tqe yjac5-2yaaa-aaaan-qaqka-cai
Memory allocation: 0 Bytes
Compute allocation: 0 %
Freezing threshold: 2_592_000 Seconds
Idle cycles burned per day: 20_548_135 Cycles
Memory Size: 2_010_735 Bytes
Balance: 2_985_407_678_380 Cycles
Reserved: 0 Cycles
Reserved cycles limit: 5_000_000_000_000 Cycles
Wasm memory limit: 3_221_225_472 Bytes
Wasm memory threshold: 0 Bytes
Module hash: 0x4f13cceb571483ac99a9f89afc05718c0a4ab72e9fac7d49054c0a3e05c4899b
Number of queries: 0
Instructions spent in queries: 0
Total query request payload size: 0 Bytes
Total query response payload size: 0 Bytes
Log visibility: controllers
The asset canister now estimates the size of the data to be serialized to stable memory, and reserves that much space for the ValueSerializer's buffer.
Updated Motoko to 0.13.7
Updated replica to elected commit 4ba583480e05a518aa2bcf36f5a0e48475e8edc2. This incorporates the following executed proposals:
- 134967
- 134966
- 134900
- 134773
- 134684
- 134663
- 134608
- 134609
- 134497
- 134408
- 134337
- 134336
- 134259
- 134251
- 134250
- 134188
- 134187
- 134186
- 134185
dfx start --pocketic is now compatible with --bitcoin-node and --enable-bitcoin.
The ledger canisters can be pulled even though they are not really "pullable".
The metadata like wasm_url and init_guide are hardcoded inside dfx deps pull logic.
- ICP ledger:
ryjl3-tyaaa-aaaaa-aaaba-cai - ckBTC ledger:
mxzaz-hqaaa-aaaar-qaada-cai - ckETH ledger:
ss2fx-dyaaa-aaaar-qacoq-cai
Allow setting permissions lists in init arguments just like in upgrade arguments.
- Module hash: 2c24b5e1584890a7965011d5d1d827aca68c489c9a6308475730420fa53372e8
- #3965
- Module hash: f45db224b40fac516c877e3108dc809d4b22fa42d05ee8dfa5002536a3a3daed
- Bump agent-js to fix error code
If users run subcommands of dfx cycles or dfx ledger without the --ic flag, show below messages to indicate what to do next.
Error explanation:
Cycles ledger with canister ID 'um5iw-rqaaa-aaaaq-qaaba-cai' is not installed.
How to resolve the error:
Run the command with '--ic' flag if you want to manage the cycles on the mainnet.
For dfx start, show below messages to users to indicate what to do next.
Success! The dfx server is running.
You must open a new terminal to continue developing. If you'd prefer to stop, quit with 'Ctrl-C'.
Updated Motoko to 0.13.4
Updated replica to elected commit a62848817cec7ae50618a87a526c85d020283fd9. This incorporates the following executed proposals:
- 134036
- 134035
- 134034
- 134032
- 133939
- 133953
- 133952
- 133951
- 133950
- 133902
- 133901
- 133900
- 133798
- 133799
- 133800
- 133457
- 133450
- 133443
- 133397
- 133396
If DFX_NETWORK is set in the environment, all commands will use that network by default.
The --network parameter will take precedence if provided.
This fixes an issue where dfx deploy --playground would fail if the project
had not been previously built for the local network.
Added support for the canister log allowed viewer list, enabling specified users to access a canister's logs without needing to be set as the canister's controller. Valid settings are:
--add-log-viewer,--remove-log-viewerand--set-log-viewerflags withdfx canister update-settings--log-viewerflag withdfx canister createcanisters[].initialization_values.log_visibility.allowed_viewersindfx.json
The frontend canister sync now tries to batch multiple small content chunks into a single call using the create_chunks method added earlier.
And for small amounts of uploaded data the asset sync can now skip chunk creation entirely.
This should lead to significantly faster upload times for frontends with many small files.
Updated Motoko to 0.13.2
SetAssetContentArguments has a new field last_chunk: opt blob which can be used in addition to chunk_ids so that small assets can be uploaded as part of commit_batch,
skipping the need to await a separate create_chunk call.
Bumped api_version to 2 for the previous addition of create_chunks since the improved file sync relies on it.
dfx start --pocketic is now compatible with --artificial-delay and the subnet_type configuration option, and enables --enable-canister-http by default.
Add the batch id in the error messages of propose_commit_batch.
Module hash: 2c9e30df9be951a6884c702a97bbb8c0b438f33d4208fa612b1de6fb1752db76
Updated Motoko to 0.13.1
Updated replica to elected commit 0a6d829cddc1534c29e0d2c3c3ebd1024bff8d1a.
This incorporates the following elected proposals:
- 133327
- 133310
- 133309
- 133144
- 133143
- 133142
- 133063
- 133062
- 133061
- 132548
- 132547
- 132507
- 132482
- 132481
- 132500
- 132416
- 132413
- 132414
- 132412
- 132376
- 132375
- 132223
- 132222
- 132149
- 132148
- 131787
- 131757
- 131697
Module hash 15da2adc4426b8037c9e716b81cb6a8cf1a835ac37589be2cef8cb3f4a04adaa
dfx canister install and dfx deploy takes options --skip-pre-upgrade and --wasm-memory-persistence.
dfx deploy --mode now takes the same possible values as dfx canister install --mode: "install", "reinstall", "upgrade" and "auto".
In "auto" mode, the upgrade options are hints which only take effects when the actual install mode is "upgrade".
To maintain backward compatibility, a minor difference between the two commands remains.
If the --mode is not set, dfx deploy defaults to "auto", while dfx canister install defaults to "install".
Report upgrade compatibility warnings for Motoko, such as deleted stable variables, in addition to compatibility errors.
Support Motoko's enhanced orthogonal persistence by automatically setting the canister upgrade option wasm_memory_persistence based on the Wasm metadata.
dfx start --pocketic no longer requires --clean, and can persist replica state between runs.
Build scripts and other scripts now always run with the working directory set to the project root (directory containing dfx.json).
This applies to the following:
- build scripts
- extension run
- tech stack value computation
- packtool (vessel, mops etc)
dfx extension list now support --available flag to list available extensions from the
extension catalog.
The extension catalog can be overridden with the --catalog-url parameter.
Added create_chunks. It has the same behavior as create_chunk, except that it takes a vec blob and returns a vec BatchId instead of non-vec variants.
Module hash: 3a533f511b3960b4186e76cf9abfbd8222a2c507456a66ec55671204ee70cae3
Updated Motoko to 0.12.1
We had to roll back part of the increased default security policy for the sveltekit starter due to the framework's use of inline scripts
The new dfx canister snapshot command can be used to create, apply, and delete snapshots of stopped canisters.
icx-proxy's HTTP gateway has been replaced with PocketIC's. (This does not impact the meaning of --pocketic in dfx start.)
Schnorr signature signing for Ed25519 is now enabled.
A test key id Ed25519:dfx_test_key is ready to be used by locally created canisters.
dfx extension install now locates extensions using the
extension catalog.
This can be overridden with the --catalog-url parameter.
Updated replica to elected commit 3d0b3f10417fc6708e8b5d844a0bac5e86f3e17d. This incorporates the following executed proposals:
Updated replica to elected commit 2c0b76cfc7e596d5c4304cff5222a2619294c8c1. This incorporates the following executed proposals:
This change has an accompanying migration guide. Please see the 0.23.0 migration guide for instructions on how to adapt your project to this feature.
It is now possible to specify a "security_policy" field in .ic-assets.json5 for asset configurations.
Valid options are "disabled", "standard", and "hardened".
The security policy provides a set of standard headers to make frontends more secure.
Headers manually specified in the "headers" field take precedence over the security policy headers.
If "security_policy" is not specified or "disabled" is set, then no headers are added. If "security_policy" is not set at all, a warning is displayed that there is no security policy set.
If "standard" is specified, a set of security headers is added to the asset. The headers can be displayed with dfx info security-policy.
It is a set of security headers that will work for most dapps. A warning is displayed that the headers could be hardened.
If "hardened" is set, the same headers as with "standard" are added.
The asset sync expects that improved headers are set that would improve security where appropriate.
If no custom headers are present the asset sync will fail with an error.
All warnings regarding security policies can be disabled with ``"disable_security_policy_warning": true`. It needs to be set per asset.
The standard/hardened security policy headers can be seen with dfx info security-policy.
It also contains a lot of suggestions on how to harden the policy.
Updated the starter projects to use "security_policy" instead of including the whole security policy by defining individual headers.
Shows the headers that get applied to assets that are configured to "security_policy": "standard" or "security_policy": "hardened" in .ic-assets.json5.
Produces output that can be directly pasted into a .json5 document.
It's now possible for dfx extension install to install an extension from
somewhere other than https://github.com/dfinity/dfx-extensions, by passing
a URL to an extension.json file rather than an extension name.
For example, these are equivalent:
dfx extension install nns
dfx extension install https://raw.githubusercontent.com/dfinity/dfx-extensions/main/extensions/nns/extension.jsonThis update also adds the optional field download_url_template to extension.json,
which dfx will use to locate an extension release archive.
However, if a version is specified with --version, and the installed version is different,
then dfx extension install will still report an error.
A recent hotfix to the CMC changed how the arguments to notify_create_canister need to be passed.
dfx now again properly calls that function.
This replaces the dashboard link, which is now shown only in verbose mode. This should hopefully be less confusing for new users.
It is now possible to specify a particular crate within a Rust package to use for a canister module, using the crate field.
This enables specifying crates with different names than the package. In a few cases these were previously auto-detected
by dfx, you will need to add this field if you were using such a setup.
The --wallet parameter can now be either a principal or the name of an identity.
If the name of an identity, dfx looks up the associated wallet's principal.
This means --wallet <name> is the equivalent of --wallet $(dfx identity get-wallet --identity <name>).
Some commands that download http resources, for example dfx extension install, will
once again display any error cause.
Now retries the following, with exponential backoff as is already done for connect and transport errors:
- 500 internal server error
- 502 bad gateway
- 503 service unavailable
- 504 gateway timeout
- 429 many requests
To do this, the @dfinity/agent version was updated as well.
dfx schema --for extension-manifestcorresponds to extension.jsondfx schema --for extension-dependenciescorresponds to dependencies.json
The NIST guidelines require passwords to be longer than 8 characters. This is now enforced when creating new identities. Identities protected by a shorter password can still be decrypted.
feat: dfx extension install now uses the extension's dependencies.json file to pick the highest compatible version
Schnorr signature signing for Bip340Secp256k1 is now enabled.
A test key id Bip340Secp256k1:dfx_test_key is ready to be used by locally created canisters.
Updated replica to elected commit 5849c6daf2037349bd36dcb6e26ce61c2c6570d0. This incorporates the following executed proposals:
Updated Motoko to 0.11.2
Introduced dfx killall, a command for killing DFX-started processes.
dfx call --query aaaaa-aa bitcoin_get_balance_query/bitcoin_get_utxos_query will result in an error.
Now displays Using the default configuration for the local shared network.
instead of Using the default definition for the 'local' shared network because ~/.config/dfx/networks.json does not define it.
chore!: Improved error message about canister ranges when directly connecting to a node on a non-root subnet
feat: dfx start for the shared local network stores replica state files in unique directories by options
The state files for different replica versions are often incompatible,
so dfx start requires the --clean argument in order to reset data when
using different replica versions or different replica options.
For the local shared network, dfx now stores replica state files in different directories, split up by replica version and options.
As an example, you'll be able to do things like this going forward:
dfx +0.21.0 start
(cd project1 && dfx deploy && dfx canister call ...)
dfx stop
dfx +0.22.0 start
# notice --clean is not required.
# even if --clean were passed, the canisters for project1 would be unaffected.
(cd project2 && dfx deploy)
# project1 won't be affected unless you call dfx in its directory
dfx stop
dfx +0.21.0 start
# the canisters are still deployed
(cd project1 && dfx canister call ...)Prior to this change, the second dfx start would have had to include --clean,
which would have reset the state of the shared local network, affecting all projects.
This also means dfx start for the shared local network won't ever require you to pass --clean.
dfx start will delete old replica state directories. At present, it retains the 10 most recently used.
This doesn't apply to project-specific networks, and it doesn't apply with --pocketic.
It doesn't apply to project-specific networks because the project's canister ids would
reset anyway on first access. If you run dfx start in a project directory where dfx.json
defines the local network, you'll still be prompted to run with --clean if using a
different replica version or different replica options.
It doesn't apply to --pocketic because PocketIC does not yet persist any data.
When uploading assets to an asset canister, dfx by default uploads .txt, .html and .js files in identity encoding but also in gzip encoding to the frontend canister if encoding saves bytes.
It is now possible to specify in .ic-assets.json which encodings are used besides identity.
Note that encodings are only used if the encoding saves bytes compared to identity or if identity is not a specified encoding.
Example: To turn off gzip for .js files and to turn on gzip for .jpg files, use this in .ic-assets.json:
{
"match": "**/*.js",
"encodings": ["identity"]
},
{
"match": "**/*.jpg",
"encodings": ["identity", "gzip"]
}Add dfx canister url subcommand to display the url of a given canister. Basic usage as below:
dfx canister url <canister>The <canister> argument specifies the name or id of the canister for which you want to display the url.
Adds support for the log_visibility canister setting, which configures which users are allowed to read a canister's logs.
Valid options are controllers and public. The setting can be used with the --log-visibility flag in dfx canister create
and dfx canister update-settings, or in dfx.json under canisters[].initialization_values.log_visibility.
Asset synchronization now not only supports identity and gzip, but also brotli encoding.
The default encodings are still
identityandgzipfor MIME types.txt,.htmland.jsidentityfor anything else
fix!: URL decoding follows the whatwg standard
Previously, the frontend canister used custom logic to decode URLs.
The logic was replaced with a dependency that follows https://url.spec.whatwg.org/#percent-decode, which is what JavaScript's new Request("https://example.com/% $").url also uses.
This also drops support for decoding %% to %. % does no longer need to be encoded.
URLs that contain invalid encodings now return 400 Bad Request instead of 500 Internal Server Error
- Module hash: 2cc4ec4381dee231379270a08403c984986c9fc0c2eaadb64488b704a3104cc0
- #3767
Updated replica to elected commit 246d0ce0784d9990c06904809722ce5c2c816269. This incorporates the following executed proposals:
dfx canister delete occasionally fails because it attempts to withdraw too many cycles from the canister before it is deleted.
Usually, dfx tries again with a larger margin of cycles, but sometimes this gets stuck.
It is now possible to use --initial-margin to manually supply a margin in case the automatic margin does not work.
Improves sync (eg. dfx deploy, icx-asset sync) performance by parallelization:
- Make asset properties query faster by parallelization, significant improvement for canisters that have many assets
- Make chunk creation process faster, by increasing parallelization 4=>25, significant improvement when deploying lots of small assets
icx-asset: add support for log levels, defaulting to info
Passing --pocketic to dfx start now starts a PocketIC server instead of the replica. PocketIC is lighter-weight than the replica and execution environment internals can be manipulated by REST commands. For more information, see the PocketIC readme.
dfx info candid-ui-url displays the URL to the Candid UI canister for an explicitly specified --network <network name> (or local by default).
chore: Improve help text of dfx identity new to include which characters are valid in identity names
The output of dfx canister status has been also changed to use consistent capitalization of words.
When uploading assets to an asset canister, dfx by default excludes directories and files with names that start with ..
dfx will start including folders with the name .well-known by default.
It is possible to override this in .ic-assets.json like this:
{
"match": ".well-known",
"ignore": true
}When creating a canister with dfx ledger create-canister --next-to on a canister that does not exist (e.g., 2vxsx-fae), then the funds are first transferred away from the users account, but the call then fails to create the new canister, and the funds are not returned to the user's account.
Updated to agent-rs 0.35.0
Updated replica to elected commit ec35ebd252d4ffb151d2cfceba3a86c4fb87c6d6. This incorporates the following executed proposals:
Rather than increasing indentation, dfx now aligns the error causes with a "Caused by: " prefix.
Also changed error types to report error causes as causes, rather than embedding their error cause in the error text.
Before:
Error: Failed while trying to deploy canisters.
Caused by: Failed while trying to deploy canisters.
Failed to build all canisters.
Failed while trying to build all canisters.
The build step failed for canister 'bw4dl-smaaa-aaaaa-qaacq-cai' (wasminst_backend) with an embedded error: Failed to build Motoko canister 'wasminst_backend'.: Failed to compile Motoko.: Failed to run 'moc'.: The command '"/Users/ericswanson/.cache/dfinity/versions/0.19.0/moc" ... params ... failed with exit status 'exit status: 1'.
Stdout:
Stderr:
/Users/ericswanson/w/wasminst/src/wasminst_backend/main2.mo: No such file or directoryAfter:
Error: Failed while trying to deploy canisters.
Caused by: Failed to build all canisters.
Caused by: Failed while trying to build all canisters.
Caused by: The build step failed for canister 'bw4dl-smaaa-aaaaa-qaacq-cai' (wasminst_backend)
Caused by: Failed to build Motoko canister 'wasminst_backend'.
Caused by: Failed to compile Motoko.
Caused by: Failed to run 'moc'.
Caused by: The command '"/Users/ericswanson/.cache/dfinity/versions/0.20.0/moc" ... params ... failed with exit status 'exit status: 1'.
Stdout:
Stderr:
/Users/ericswanson/w/wasminst/src/wasminst_backend/main2.mo: No such file or directoryAdds support for the wasm_memory_limit canister setting, which limits the canister's heap during most calls but does not affect queries. As with other canister settings, it can be set in dfx canister create or dfx canister update-settings via the --wasm-memory-limit flag, as well as in dfx.json under canisters[].initialization_values.wasm_memory_limit.
Please see extension-defined-canister-types for details.
Introduces support for the init_arg_file field in dfx.json, providing an alternative method to specify initialization arguments.
This field accepts a relative path, from the directory containing the dfx.json file.
Note
- Only one of
init_argandinit_arg_filecan be defined at a time. - If
--argumentor--argument-fileare set, the argument from the command line takes precedence over the one in dfx.json.
dfx new could fail with "Failed to scaffold frontend code" if node was installed but npm was not installed.
Updated cycles wallet to a gzipped version of 20240410 release:
- Module hash:
7745d3114e3e5fbafe8a7150a0a8c15a5b8dc9257f294d5ced67d41be76065bc, in gzipped form:664df1045e093084f4ebafedd3a793cc3b3be0a7ef1b245d8d3defe20b33057c - https://github.com/dfinity/cycles-wallet/commit/b013764dd827560d8538ee2b7be9ecf66bed6be7
Updated replica to elected commit 5e285dcaf77db014ac85d6f96ff392fe461945f5. This incorporates the following executed proposals:
In the remote canister declaration it is possible to set a candid file to use when the canister is remote on a specific network.
dfx now correctly sets the CANISTER_CANDID_PATH_<canister name> environment variable during the build process on remote networks if the file exists.
dfx schema --for dfx-metadata to display JSON schema of the "dfx" metadata.
The standardized dfx metadata is extended with another object: tech_stack.
Please check tech-stack for more details.
This command generates shell completion scripts for bash, elvish, fish, zsh, or PowerShell.
Describing how to install shell completion scripts is beyond the scope of this document. Here are two commands that would enable command completion in the current shell:
In zsh:
source <(dfx completion zsh)In bash:
source <(dfx completion)Previously, dfx would always create a .dfx directory in the project root if dfx.json was present.
Now, it only does so if the command accesses the .dfx directory in some way.
For example, this will work now:
echo garbage >dfx.json && dfx identity get-principalUpdated replica to elected commit 02dcaf3ccdfe46bd959d683d43c5513d37a1420d. This incorporates the following executed proposals:
dfx canister call --query defaults to use "Replica-signed query" feature.
It doesn't work with bitcoin query calls to the management canister because the Boundary Nodes cannot route the read_state call.
Only for these particular queries, dfx will make the query calls without checking the replica signatures.
If the response reliability is a concern, you can make update calls to the secure alternatives.
If the environment variable DFX_CYCLES_LEDGER_SUPPORT_ENABLE is set and no cycles wallet is configured, then dfx will try to use the cycles ledger to perform any operation that the cycles wallet usually is used for.
The following commands/options have been unhidden:
dfx cycles--from-subaccountfordfx deploy,dfx canister create,dfx canister deposit-cyclesto determine which cycles ledger subaccount the used cycles should be used from--created-at-timefordfx deploy,dfx create canister,dfx canister deposit-cyclesto control transaction deduplication on the cycles ledger--to-subaccountfordfx canister deleteto control into which subaccount cycles are withdrawn before the canister is deleted
The cycles ledger will not be supported by default until the cycles ledger canister is under NNS control.
This is the same as dfx canister call ... | idl2json, for convenience.
See also: https://github.com/dfinity/idl2json
Added commas in between fields, and newlines to improve formatting.
dfx canister status now outputs to stdout, rather than stderr, so that its output is grep compatible.
dfx canister logs now outputs to stdout, rather than stderr, so that its output is grep and tail compatible.
The management canister method fetch_canister_logs can be called only as a query, not as an update call. Therefore, dfx canister logs <canister_id> now uses a query call for this purpose.
DFX no longer forbids hyphens in project names. Anywhere they appear as the name of a variable, e.g. environment variables or generated JS variables, they will be replaced with underscores.
Previously, any configuration element in .ic-assets.json functioned as if a setting of
"allow_raw_access": true were present in the json object.
For example, given the following configuration, all files would be configured
with allow_raw_access set to true, as if the second entry specified
"allow_raw_access": true (which is the default), even though it does not.
[
{
"match": "**/*",
"allow_raw_access": false
},
{
"match": "**/*",
"headers": {
"X-Anything": "Something"
}
}
]Now, given the same configuration, all files would be configured with allow_raw_access set to false, as expected.
Note that the default value of allow_raw_access is still true.
Removed the logic for calling a different version of dfx based on DFX_VERSION or the dfx field in
dfx.json. This is now performed by dfxvm.
When all the arguments are optional, dfx automatically provides a null value when no arguments are provided.
--always-assist flag enables the candid assist feature for optional arguments, instead of providing a default null value.
When the dependency has been in the cache, dfx deps pull forgot to set correct wasm_hash_download in pulled.json.
It caused the following init/deploy commands to fail.
Updated replica to elected commit 425a0012aeb40008e2e72d913318bc9dbdf3b4f4. This incorporates the following executed proposals:
Downgraded Bitcoin canister to release/2023-10-13
Updated Motoko to 0.11.1
The dfx upgrade command now prints a message directing the user to install dfxvm.
In dfx 0.14.0, we standardized on CANISTER_ID_<CANISTER_NAME_UPPERCASE> and
CANISTER_CANDID_PATH_<CANISTER_NAME_UPPERCASE> for
environment variables for canister IDs and candid paths respectively,
and deprecated the old formats. This version removes the old formats.
The only variable names now provided are the following, all uppercase, with any '-' replaced by '_':
CANISTER_CANDID_PATH_<CANISTER_NAME>CANISTER_ID_<CANISTER_NAME>
For reference, these formats were removed (any '-' characters were replaced by '_'):
CANISTER_CANDID_PATH_<canister_name_case_from_dfx_json><CANISTER_NAME_UPPERCASE>_CANISTER_ID
There is a new subcommand logs to fetch canister's logs.
When printing the log entries it tries to guess if the content can be converted to UTF-8 text and prints an array of hex bytes if it fails.
Note
This feature is still in development. Changes may occur in following releases.
Locally, canisters can either be accessed via <canister_id>.localhost:<port> or localhost:<port>?canisterId=<canister_id>.
The query parameter format is annoying to handle in SPAs, therefore the subdomain format is now displayed alongside the subdomain version after deployments.
The query parameter format is not removed because Safari does not support localhost subdomains.
Made it so dfx deploy and dfx canister install will always write
environment variables for all canisters in the project that have canister ids
to the .env file, even if they aren't being deployed/installed
or a dependency of a canister being deployed/installed.
There are a few subcommands that take --argument/--argument-file options to set canister call/init arguments.
We unify the related logic to provide consistent user experience.
The notable changes are:
dfx deploynow accepts--argument-file.dfx deps initnow accepts--argument-file.
Ask for user input when Candid argument is not provided in dfx canister call, dfx canister install and dfx deploy.
Previously, we cannot call dfx deploy --all when multiple canisters require init args, unless the init args are specified in dfx.json. With the Candid assist feature, dfx now asks for init args in terminal when a canister requires init args.
fix: restored access to URLs like http://localhost:8080/api/v2/status through icx-proxy
Pinned icx-proxy at 69e1408347723dbaa7a6cd2faa9b65c42abbe861, shipped with dfx 0.15.2
This means commands like the following will work again:
curl -v --http2-prior-knowledge "http://localhost:$(dfx info webserver-port)/api/v2/status" --output -
It is now possible to approve other principals to spend cycles on your behalf using dfx cycles approve <spender> <amount>.
dfx cycles transfer now also supports --from, --from-subaccount, and --spender-subaccount.
For detailed explanations on how these fields work please refer to the ICRC-2 specification.
The script at https://internetcomputer.org/install.sh now installs the dfxvm version manager instead of the dfx binary.
dfx deps pull was recently changed to allow hash mismatch wasm. But init and deploy weren't change accordingly.
Also the warning of hash mismatch is removed since it scares users and users can't fix it locally.
Fixed a bug where dfx generate would delete a canister's source candid file if the declarations.bindings in dfx.json did not include "did".
Fixed a bug where dfx canister install would fail when specify a canister id and there is no dfx.json.
Fixed a bug where dfx canister call would fail when the deployed canister was removed from dfx.json.
Fix the Typescript binding for init args.
Updated replica to elected commit d966b2737ca75f1bfaa84f21e7f3f7c54b5d7f33. This incorporates the following executed proposals:
Updated Motoko to 0.11.0
Module hash: 32e92f1190d8321e97f8d8f3e793019e4fd2812bfc595345d46d2c23f74c1ab5
bump ic-cdk to 0.13.1
Module hash: 1208093dcc5b31286a073f00f748ac6612dbae17b66c22332762705960a8aaad
bump ic-cdk to 0.13.1
Updated Bitcoin canister to release/2024-01-22
dfx new now has a new set of customizable project templates and an interactive menu for selecting them. Supports the Svelte, Vue, and React frameworks, and Azle and Kybra backends.
Previously dfx new --no-frontend still created a frontend canister. This behavior is now accessed via --frontend simple-assets.
It is now possible to redeem faucet coupons to cycles ledger accounts.
It is now possible to turn ICP into cycles that are stored on the cycles ledger using dfx cycles convert --amount <amount of ICP>
In addition to passing --specified-id in dfx deploy and dfx canister create, specified_id can be set in dfx.json.
If it is set in both places, the specified ID from the command line takes precedence over the one in dfx.json.
dfx deploy, dfx canister create, and dfx ledger create-canister now support the option --next-to <canister principal> to create canisters on the same subnet as other canisters.
The registry canister is used as the source of truth to figure out the subnet id.
In addition to passing --argument or --argument-file in dfx deploy and dfx canister install, init_arg can be set in dfx.json.
If it is set in both places, the argument from the command line takes precedence over the one in dfx.json.
Providers can set an optional init_arg field in pullable metadata.
When consumers run dfx deps init without --argument, the value in init_arg will be used automatically.
Consumers won't have to figure out the init argument by themselves. It can be overwritten by dfx deps init --argument.
For pulled canisters which have no init_arg in pullable metadata, dfx deps init without --argument will try to set "(null)" automatically.
This works for canisters with top-level opt in init argument. This behavior is consistent with dfx deploy and dfx canister install.
The init argument can be overwritten by dfx deps init --argument.
It is natural to point wasm_hash_url to the <FILE>.sha256 file generated by shasum or sha256sum which consists of the hash and the file name.
Now when dfx deps pull, such content will be accept properly.
If the latest release of https://github.com/dfinity/dfxvm is >= 1.0, dfx upgrade will
direct the user to install dfxvm and then exit.
dfx canister call will always fetch the .did file from the canister metadata. If the canister doesn't have the candid:service metadata, dfx will fallback to the current behavior of reading the .did file from the local build artifact. This fallback behavior is deprecated and we will remove it in a future release. This should not affect Motoko and Rust canisters built from dfx, as dfx build automatically writes the Candid metadata into the canister.
If you build with custom canister type, add the following into dfx.json:
"metadata": [
{
"name": "candid:service"
}
]
If you build the canister without using dfx, you can use ic-wasm to store the metadata:
ic-wasm canister.wasm -o canister.wasm metadata candid:service -f service.did -v public
Please use the dfx version manager instead.
The dfxvm install script now accepts DFXVM_INIT_YES=<non empty string> to skip confirmation.
When using dfx canister status, the output now includes the new query statistics. Those might initially be 0, if the feature is not yet enabled on the subnet the canister is installed in.
Fix the bug that when parsing vec \{1;2;3\} with blob type, dfx silently ignores the numbers.
If the local did file contains import or init args, dfx will rewrite the did file when storing in canister metadata.
Due to current limitations of the Candid parser, comments will be dropped during rewriting.
If the local did file doesn't contain import or init args, we will not perform the rewriting, thus preserving the comments.
The following commands now work outside of a project:
dfx canister start <specific canister id>dfx canister stop <specific canister id>dfx canister deposit-cycles <amount> <specific canister id>dfx canister uninstall-code <specific canister id>
Updated replica to elected commit 044cfd5147fc97d7e5a214966941b6580c325d72. This incorporates the following executed proposals:
Module hash: e5f049a97041217554c1849791c093c4103a6844625be3d6453df2e91abeed35
Fix the HTTP header for deploying in remote environments
When using dfx deploy or dfx canister install, previously Wasm modules larger than 2MiB would be rejected.
They are now automatically submitted via the chunking API if they are large enough.
From a user perspective the limitation will simply have been lifted.
Providers can provide the hash through wasm_hash_url instead of hard coding the hash directly.
If the hash of downloaded wasm doesn’t match the provided hash (wasm_hash, wasm_hash_url or read from mainnet state tree), dfx deps won’t abort. Instead, it will print a warning message.
dfx deploy, dfx canister create, and dfx ledger create-canister now support the option --subnet <subnet principal> to create canisters on specific subnets.
dfx canister create and dfx deploy now support the option --subnet-type <subnet type> to create canisters on a random subnet of a certain type.
Use dfx ledger show-subnet-types to list the available subnet types
The dfx cycles command no longer needs nor accepts the --cycles-ledger-canister-id <canister id> parameter.
This was deprecated in dfx 0.15.1.
Updated to candid 0.10, ic-cdk 0.12, and ic-cdk-timers 0.6
They've always been stored with nanosecond precisions on Linux and Macos. Now they are stored with nanosecond precision on Windows too.
fix: dfx canister delete, when using an HSM identity, no longer fails by trying to open two sessions to the HSM
Previously, this would fail with a PKCS#11: CKR_CRYPTOKI_ALREADY_INITIALIZED error.
Updated Motoko to 0.10.4
Module hash: 3c86d912ead6de7133b9f787df4ca9feee07bea8835d3ed594b47ee89e6cb730
Module hash: b91e3dd381aedb002633352f8ebad03b6eee330b7e30c3d15a5657e6f428d815
Fix the routing error when deploying to gitpod/github workspace. Fix that Candid UI cannot be opened using localhost URL.
Updated replica to elected commit 324eb99eb7531369a5ef75560f1a1a652d123714. This incorporates the following executed proposals:
This will enable browsing the asset canister at http://<canister-id>.localhost:<port> in most browsers.
Previously, dfx ledger top-up only accepted canister principals. Now it accepts both principals and canister names.
A change to curl --help output made it so the install script did not detect
that the --proto and --tlsv1.2 options are available.
When dfx deletes a canister, it first withdraws as many cycles as possible from the canister. While doing so, dfx previously set the memory allocation of the canister to 8GB in order to not run into any memory problems while withdrawing. This, however, lead to problems with dynamic memory pricing in subnets with a lot of data because then it becomes very expensive to reserve that much data. dfx now no longer sets a memory allocation. We anticipate fewer problems this way.
In order to access a local replica through a domain name or domain names,
it's necessary to pass the --domain parameter to icx-proxy. dfx now supports
this in configuration and as a parameter to dfx start. You can specify a single
domain or a list of domains in any of the following ways:
- in networks.json, in
.<network>.proxy.domain - in dfx.json, in
.networks.<network>.proxy.domain - in dfx.json, in
.defaults.proxy.domain - to dfx start, as
dfx start --domain <domain1> --domain <domain2> ...
- Module hash: d172df265a14397a460b752ff07598380bc7ebd9c43ece1e82495ae478a88719c
- Internet identity integration in Candid UI. Thanks to @Web3NL!
- You can customize the II url and derivationOrigin via URL parameter
iiandoriginrespectively.
- You can customize the II url and derivationOrigin via URL parameter
- Update with the new profiling API
Updated Motoko to 0.10.3
Previously, deleting a canister in the project by id rather than by name
would leave the canister id in the canister id store. This would cause
dfx deploy to fail.
Running dfx cache delete && dfx extension install nns would previously
create a cache directory containing only an extensions subdirectory.
dfx only looks for the existence of a cache version subdirectory to
determine whether it has been installed. The end result was that later
commands would fail when the cache did not contain expected files.
The .env file location, whether specified as output_env_file in dfx.json
or --output-env-file <file> on the commandline, is now considered relative
to the project root, rather than relative to the current working directory.
Enables passing large arguments that cannot be passed directly in the command line using the --argument-file flag. For example dfx canister install --argument-file ./my/argument/file.txt my_canister_name.
This requires the list_authorized and list_permitted methods to be called as an update and disables the ability to
call it as a query call. This resolves a potential security risk.
fix: dfx ledger transfer now logs to stderr messages about duplicates rather than printing them to stdout
The message "transaction is a duplicate of another transaction in block ...", previously printed to stdout, is now logged to stderr. This means that the output of dfx ledger transfer to stdout will contain only Transfer sent at block height <block height>.
Underscores (_) can now be used to make large numbers more readable. For example: dfx canister deposit-cycles 1_234_567 mycanister
Certain suffixes that replace a number of zeros are now supported. The (case-insensitive) suffixes are:
kfor000, e.g.500kmfor000_000, e.g.5mbfor000_000_000, e.g.50Btfor000_000_000_000, e.g.0.3T
For cycles an additional c or C is also acceptable. For example: dfx canister deposit-cycles 3TC mycanister
This won't work on mainnet yet, but can work locally after installing the cycles ledger.
Added the following subcommands:
dfx cycles balancedfx cycles transfer <to> <amount>(transfer cycles from one account to another account)dfx cycles top-up <to> <amount>(send cycles from an account to a canister)
Updated Motoko to 0.10.2
Defining a custom etag header no longer breaks certification.
Fixed a certification issue where under certain conditions the fallback file (/index.html) was served with an incomplete certificate tree, not proving sufficiently that the fallback file may be used as a replacement.
Add the option to (re)set all permissions using upgrade arguments. This is especially useful for SNSes that cannot make calls as the canister's controller.
- Module hash: 657938477f1dee46db70b5a9f0bd167ec5ffcd2f930a1d96593c17dcddef61b3
- #3443
- #3451
- #3429
- #3428
- #3421
Updated replica to elected commit 69e1408347723dbaa7a6cd2faa9b65c42abbe861. This incorporates the following executed proposals:
Updated Bitcoin canister to release/2023-10-13
dfx canister status will now display the reserved cycles balance and reserved cycles limit for a canister.
Added command-line options:
dfx canister create --reserved-cycles-limit <limit>dfx canister update-settings --reserved-cycles-limit <limit>
In addition, dfx deploy will set reserved_cycles_limit when creating canisters if specified in canisters.<canister>.initialization_values.reserved_cycles_limit in dfx.json.
import management "ic:aaaaa-aa;
This will automatically produce the idl in the .dfx folder.
Generate frontend declarations for remote canisters too because frontend JS code may want to call them.
Install a specific version of an extension, bypassing version checks.
The Unknown lookup of a path in a certificate results in an AgentError (the IC returns Absent for non-existing paths).
Added warning that the --emulator is deprecated and will be discontinued soon.
Updates node engines to reflect the same engines supported in agent-js.
"node": "^12 || ^14 || ^16 || >=17",
"npm": "^7.17 || >=8"
Introduced a new network type called playground. Canisters on such networks are not created through standard means, but are instead borrowed from a canister pool.
The canisters time out after a while and new canisters need to be borrowed for further deployments.
To define custom playground networks, use a network definition that includes the playground key:
"<network name>": {
"playground": {
"playground_canister": "<canister pool id>",
"timeout_seconds": <amount of seconds after which a canister is returned to the pool>
}
}Introduced a new network that is available by default called playground. Additionally, --playground is an alias for --network playground.
By default, this network targets the Motoko Playground backend to borrow canisters. The borrowed canisters will be available for 20 minutes, and the timer restarts on new deployments.
When the timer runs out the canister(s) will be uninstalled and are returned to the pool.
Any commands that allow choosing a target network (e.g. dfx canister call) require --playground or --network playground in order to target the borrowed canister(s).
Use dfx deploy --playground to deploy simple projects to a canister borrowed from the Motoko Playground.
For example, dfx deploy --ic rather than dfx deploy --network ic.
Background: In order to determine whether to start a project-specific network or the shared network, dfx start looks for the local network in dfx.json.
- If found,
dfx startstarts the project-specific local network, applying anydefaultsfrom dfx.json. - If there is no dfx.json, or if dfx.json does not define a
localnetwork,dfx startstarts the shared network. Because the shared network is not specific to any project,dfx startignores any other settings from dfx.json, includingdefaults.
If dfx start is starting the shared network from within a dfx project, and that dfx.json contains settings in the defaults key for bitcoin, replica, or canister_http, then dfx start will warn that it is ignoring those settings. It will also describe how to define equivalent settings in networks.json.
The parameter was erroneously passed twice. Now it is passed only once.
Removed this warning: "Project-specific networks are deprecated and will be removed after February 2023." While we may remove project-specific networks in the future, it is not imminent. One key requirement is the ability to run more than one subnet type at one time.
Updated to a version of the icx-proxy that is released with the replica and other related binaries.
Changes in behavior:
- "%%" is no longer accepted when url-decoding filenames for the asset canister. Though curl supports this, it's not part of the standard. Please replace with %25.
- The icx-proxy now performs response verification. This has exposed some bugs in the asset canister. However, since this new icx-proxy matches what the boundary nodes use, this will better match the behavior seen on the mainnet.
- Bugs that this has exposed in the asset canister:
- after disabling aliasing for an asset, the asset canister will return an incorrect certification in the 404 response.
- after setting a custom "etag" header in .ic-assets.json, the asset canister will return an incorrect certification in the 200 response.
- assets with certain characters in the filename (example: "æ") will no longer be served correctly. The definition of "certain characters" is not yet known.
- Module hash: 934756863c010898a24345ce4842d173b3ea7639a8eb394a0d027a9423c70b5c
- Add
merge_init_argsmethod in Candid UI. - Draw flamegraph for canister upgrade.
For certification v1, if none of the requested encoding are certified but another encoding is certified, then the frontend canister once again returns the certificatie even though the response hash won't match.
This allows the verifying side to try to transform the response such that it matches the response hash.
For example, if only the encoding gzip is requested but the identity encoding is certified, the gzip encoding is returned with the certificate for the identity encoding.
The verifying side can then unzip the response and will have a valid certificate for the identity response.
Updated replica to elected commit 91bf38ff3cb927cb94027d9da513cd15f91a5b04. This incorporates the following executed proposals:
The use-old-metering flag enables old metering in replica. The new metering is enabled in the starter by default, so this flag is to compare the default new metering with the old one.
The flag is temporary and will be removed in a few months.
fix: added https://icp-api.io to the default Content-Security-Policy header
Existing projects will need to change this value in .ic-assets.json or .ic-assets.json5 to include https://icp-api.io
All projects will need to redeploy.
The default value for allow_raw_access is now true. This means that by default, the frontend canister will no longer restrict the access of traffic to the <canister-id>.raw.icp0.io domain, and will no longer automatically redirect all requests to the certified domain (<canister-id>.icp0.io), unless configured explicitly.
Note that existing projects that specify "allow_raw_access": false in .ic-assets.json5 will need to change or remove this value manually in order to allow raw access.
Both have now been turned into the dfx extensions. In order to obtain them, please run dfx extension install nns and dfx extension install sns respectively. After the installation, you can use them as you did before: dfx nns ..., and dfx sns ....
Use dfx start instead. If you have a good reason why we should keep these commands, please contribute to the discussion at #3163
A previous change made dfx wait after installing a canister until the replica updated its reported module hash, but this change did not affect wallets. Now dfx waits for wallets too, to eliminate a class of wallet installation errors.
Early break out from actors starting procedure.
It's now possible to suppress warnings of this form:
WARN: The <identity> identity is not stored securely. Do not use it to control a lot of cycles/ICP. Create a new identity with `dfx identity new` and use it in mainnet-facing commands with the `--identity` flag
To do so, export the environment variable DFX_WARNING with the value -mainnet_plaintext_identity.
export DFX_WARNING="-mainnet_plaintext_identity"Note that this can be combined to also disable the dfx version check warning:
export DFX_WARNING="-version_check,-mainnet_plaintext_identity"New identities like dfx identity new my/identity or dfx identity new 'my identity' can easily lead to problems, either for dfx internals or for usability.
New identities are now restricted to the characters ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz.-_@0123456789.
Existing identities are not affected by this change.
NOTE: We've re-enabled response verification v2 in the asset canister.
Best explained by an example: Two assets exist with aliasing enabled: /content and /content.html. Usually, when requesting /content, /content.html is served because it has aliasing enabled.
But in this scenario, because /content exists, it overwrites the alias and /content is served when requesting the path /content.
When the file /content is deleted, /content is once again a valid alias of /content.html.
Previously, the alias of /content.html was not properly updated in the certification tree, making /content inaccessible.
Certification v2 allows certifying arbitrary responses. If the requested file does not exist, and the fallback file (/index.html) does not exist either,
the frontend canister serves a HTTP 404 response. This response was previously not certified.
Previously, the operation was a no-op if the content type matched, but ignored other, possibly different, asset properties. Now, it fails with an error.
The http_request_streaming_callback() and get_chunk() methods use the sha256 parameter to ensure that the chunks they return are part of the same asset contents returned by the initial call. This parameter is now required to be Some(hash).
For http_request() and http_request_streaming_callback(), there should be no change: all callers of http_request_streaming_callback() are expected to pass the entire token returned by http_request(), which includes the sha256 parameter.
Any callers of get_chunk() should make sure to always pass the sha256 value returned by the get() method. It will always be present.
Updated Motoko to 0.9.7
- Module hash: b9173bb25dabe5e2b736a8f2816e68fba14ca72132f5485ce7b8f16a85737a17
- #3260
- #3252
- dfinity/candid#449
- dfinity/candid#453
- Module hash: e20be8df2c392937a6ae0f70d20ff23b75e8c71d9085a8b8bb438b8c2d4eafe5
- #3337
- #3298
- #3256
- #3252
- #3249
- #3212
- #3227
Updated replica to elected commit cabe2ae3ca115b1a3f24d75814d4f8e317b2964d. This incorporates the following executed proposals:
Please use dfx start instead, which is a combination of the two commands.
If you have a good reason why we should keep these commands, please contribute to the discussion at #3163
The custom build command can be set in dfx.json the same way it is set for custom type canisters. If the command is not provided, DFX will fallback to the default npm run build command.
{
"canisters": {
"ui": {
"type": "assets",
"build": ["<custom build command>"]
}
}
}If dfx deploy detects duplicate assets in the dist/ and frontend assets/ directories, it will now suggest upgrade steps.
After specific canister builder output wasm and candid file, dfx will do some post processing on the candid file.
The complete IDL will be copied into .dfx folder with name constructor.did.
It will be used for type checking during canister installation.
Then it is separated into two parts: service.did and init_args.txt, corresponding to canister metadata candid:service and candid:args.
service.did will be imported during dependent canisters building. And it will also be used by the Motoko LSP to provide IDE support.
NOTE: We've disabled response verification v2 in the asset canister while we improve test coverage.
The redirect from .raw.ic0.app now redirects to .ic0.app instead of .icp0.io
The validate_commit_proposed_batch() method no longer requires any permission to call.
The asset canister now enforces limits during upload. These limits to not apply to assets already uploaded.
Unconditional limits:
create_batch()now fails ifdfx deploy --by-proposalgot as far as callingpropose_commit_batch(), and the batch has not since been committed or deleted.
Configurable limits:
max_batches: limits number of batches being uploaded.max_chunks: limits total number of chunks across all batches being uploaded.max_bytes: limits total size of content bytes across all chunks being uploaded.
Added methods:
configure()to set limitsvalidate_configure(): companion method for SNSget_configuration(): to view limits
Suggestions for configured limits:
- dapps controlled by SNS: max_batches=1; max_chunks and max_bytes based on asset composition.
- dapps not controlled by SNS: unlimited (which is the default)
Note that as always, if dfx deploy does not completely upload and commit a batch, the asset canister will retain the batch until 5 minutes have passed since the last chunk was uploaded. If you have configured limits and the combination of an unsuccessful deployment and a subsequent attempt would exceed those limits, you can either wait 5 minutes before running dfx deploy again, or delete the incomplete batch with delete_batch().
Previously, the requested path was used to construct the expr_path for the index.html fallback route. This was incorrect, as the expr_path should be the path of the index.html file itself in this case.
Previously, it would only retry when waiting for the request to complete.
Previously, errors were assumed to be retryable, except for a few specific error messages and 403/unauthorized responses. This could cause deployment to appear to hang until timeout.
Now, only transport errors and timeout errors are considered retryable.
- Module hash: 1286960c50eb7a773cfb5fdd77cc238588f39e21f189cc3eb0f35199a99b9c7e
- #3205
- #3198
- #3154
- #3158
- #3144
Updated ic-ref to 0.0.1-a9f73dba
Updated cycles wallet to 20230530 release:
- Module hash: c1290ad65e6c9f840928637ed7672b688216a9c1e919eacbacc22af8c904a5e3
- https://github.com/dfinity/cycles-wallet/commit/313fb01d59689df90bd3381659d94164c2a61cf4
Updated Motoko to 0.9.3
Updated replica to elected commit ef8ca68771baa20a14af650ab89c9b31b1dc9a5e. This incorporates the following executed proposals:
When running dfx canister delete on a canister that has not been stopped, dfx will now confirm the deletion instead of erroring.
dfx can gzip wasm module as the final step in building canisters.
This behavior is disabled by default.
You can enable it in dfx.json:
{
"canisters" : {
"app" : {
"gzip" : true
}
}
}You can still specify .wasm.gz file for custom canisters directly. If any metadata/optimize/shrink options are set in dfx.json, the .wasm.gz file will be decompressed, applied all the wasm modifications, and compressed as .wasm.gz in the end.
Removed dfx deploy's behavior of providing the same argument to all canisters, and dfx canister install's behavior of providing an empty argument to all canisters regardless of what was specified. Now installing multiple canisters and providing an installation argument is an error in both commands.
Updated the command-parsing library to v4. Some colors may be different.
This feature was named dfx pull before. To make a complete, intuitive user experience, we present a set of subcommands under dfx deps:
dfx deps pull: pull the dependencies from mainnet and generatedeps/pulled.json, the candid files of direct dependencies will also be put intodeps/candid/;dfx deps init: set the init arguments for the pulled dependencies and save the data indeps/init.json;dfx deps deploy: deploy the pulled dependencies on local replica with the init arguments recorded indeps/init.json;
All generated files in deps/ are encouraged to be version controlled.
dfx nns install installs a set of canisters in a local replica. dfx nns import complements this by setting the canister IDs so that they can be queried by the user. But dfx nns import is incomplete. Now it will also provide the IDs of the nns-dapp and internet_identity canisters.
Previously the .env file only included canister IDs for canisters that were listed as explicit dependencies during the build process.
Now all canisters that have a canister ID for the specified network are included in .env.
Removing oneself (or the wallet one uses) can result in the loss of control over a canister.
Therefore dfx canister update-settings now asks for extra confirmation when removing the currently used principal/wallet from the list of controllers.
To skip this check in CI, use either the --yes/-y argument or use echo "yes" | dfx canister update-settings <...>.
If the replica does not report healthy at least once after launch, dfx will terminate and restart it.
This is required for future replica versions.
Adds a new field canister_init_arg to the bitcoin configuration in dfx.json and networks.json. Its default is documented in the JSON schema and is appropriate for the canister wasm bundled with dfx.
Cleaned up documentation of IC SDK.
Now, dfx deploy -v (or -vv) will print the following information:
- The count for each
BatchOperationKindinCommitBatchArgs - The number of chunks uploaded and the total bytes
- The API version of both the
ic-assetand the canister - (Only for
-vv) The value ofCommitBatchArgs
fix: Commit batches incrementally in order to account for more expensive v2 certification calculation
In order to allow larger changes without exceeding the per-message instruction limit, the sync process now:
- sets properties of assets already in the canister separately from the rest of the batch.
- splits up the rest of the batch into groups of up to 500 operations.
Previously, it would only retry when waiting for the request to complete.
Previously, errors were assumed to be retryable, except for a few specific error messages and 403/unauthorized responses. This could cause deployment to appear to hang until timeout.
Now, only transport errors and timeout errors are considered retryable.
The asset canister now properly removes the v2-certified response when /index.html is deleted.
Fix: The fallback file (/index.html) will now be served when using certification v2 if the requested path was not found.
The HttpResponse type now explicitly mentions the upgrade : Option<bool> field instead of implicitly returning None all the time.
The asset canister no longer needs to use await for access control checks. This will speed up certain operations.
Updated Motoko to 0.8.8
Updated replica to elected commit b3b00ba59c366384e3e0cd53a69457e9053ec987. This incorporates the following executed proposals:
- 122529
- 122284
- 122198
- 120591
- 119318
- 118023
- 116294
- 116135
- 114479
- 113136
- 111932
- 111724
- 110724
- 109500
- 108153
- 107668
- 107667
- 106868
- 106817
- 105666
- 104470
- 103281
- 103231
- 101987
Add option to specify an "optimize" field for canisters to invoke the wasm-opt optimizer through ic-wasm.
This behavior is disabled by default.
If you want to enable this behavior, you can do so in dfx.json:
"canisters": {
"app": {
"optimize" : "cycles"
}
}The options are "cycles", "size", "O4", "O3", "O2", "O1", "O0", "Oz", and "Os". The options starting with "O" are the optimization levels that wasm-opt provides. The "cycles" and "size" options are recommended defaults for optimizing for cycle usage and binary size respectively.
- Updates the starter project for env vars to use the new
dfx build&dfx deployenvironment variables - Changes the format of the canister id env vars to be
CANISTER_ID_<canister_name_uppercase>, for the frontend declaraction file to be consistent with the dfx environment variables.CANISTER_IDas both a prefix and suffix are supported for backwards compatibility.
If the network configuration has changed since last time dfx start was run, dfx start will now error if you try to run it without --clean, to avoid spurious errors. You can provide the --force flag if you are sure you want to start it without cleaning state.
The local replica uses a 600ms delay by default when performing update calls. With dfx start --artificial-delay <ms>, you can decrease this value (e.g. 100ms) for faster integration tests, or increase it (e.g. 2500ms) to mimick mainnet latency for e.g. UI responsiveness checks.
When creating a canister on non-mainnet replica, you can now specify the canister ID.
dfx canister create <CANISTER_NAME> --specified-id <PRINCIPAL>
dfx deploy <CANISTER_NAME> --specified-id <PRINCIPAL>
You can specify the ID in the range of [0, u64::MAX / 2].
If not specify the ID, the canister will be created in the range of [u64::MAX / 2 + 1, u64::MAX].
This canister ID allocation behavior only applies to the replica, not the emulator (ic-ref).
dfx nns install now takes an option --ledger-accounts to initialize the ledger canister with these accounts.
ic-cdk-timers is included in the dependencies.
By default, DFX now uses the icp0.io domain to connect to Internet Computer as opposed to using ic0.app.
Canisters communicating with ic0.app will continue to function nominally.
Previously, canisters required that the canister was created before dfx generate could be called.
As a result, the --network parameter does not have an impact on the result of dfx generate anymore.
This means that dfx generate now also generates type declarations for remote canisters.
The build field in custom canisters was already optional in code, but this fixes it in the schema.
By specifying the --no-asset-upgrade flag in dfx deploy or dfx canister install, you can ensure that the asset canister itself is not upgraded, but instead only the assets themselves are installed.
The identity may be specified using the environment variable DFX_IDENTITY.
Added the ability to configure the Wasm module used for assets canisters through the environment variable DFX_ASSETS_WASM.
fix: ledger transfer duplicate transaction prints the duplicate transaction response before returning success to differentiate between a new transaction response and between a duplicate transaction response.
Before it was possible that a user could send 2 ledger transfers with the same arguments at the same timestamp and both would show success but there would have been only 1 ledger transfer. Now dfx prints different messages when the ledger returns a duplicate transaction response and when the ledger returns a new transaction response.
This supports asset updates through SNS proposal.
Uploads asset changes to an asset canister (propose_commit_batch()), but does not commit them.
The SNS will call commit_proposed_batch() to commit the changes. If the proposal fails, the caller of dfx deploy --by-proposal should call delete_batch().
Builds the specified asset canister, determines the batch operations required to synchronize the assets, and computes a hash ("evidence") over those batch operations. This evidence will match the evidence computed by dfx deploy --by-proposal, and which will be specified in the update proposal.
No permissions are required to compute evidence, so this can be called with --identity anonymous or any other identity.
Added validate_take_ownership() method so that an SNS is able to add a custom call to take_ownership().
Added is_aliased field to get_asset_properties and set_asset_properties.
Added partial support for proposal-based asset updates:
- Batch ids are now stable. With upcoming changes to support asset updates by proposal, having the asset canister not reuse batch ids will make it easier to verify that a particular batch has been proposed.
- Added methods:
propose_commit_batch()stores batch arguments for later commitdelete_batch()deletes a batch, intended for use after compute_evidence if cancellation neededcompute_evidence()computes a hash ("evidence") over the proposed batch arguments. Once evidence computation is complete, batch will not expire.commit_proposed_batch()commits batch previously proposed (must have evidence computed)validate_commit_proposed_batch()required validation method for SNS
Added api_version endpoint. With upcoming changes we will introduce breaking changes to asset canister's batch upload process. New endpoint will help ic-asset with differentiation between API version, and allow it to support all versions of the asset canister.
Added support for v2 asset certification. In comparison to v1, v2 asset certification not only certifies the http response body, but also the headers. The v2 spec is first published in this PR
Added canister metadata field supported_certificate_versions, which contains a comma-separated list of all asset certification protocol versions. You can query it e.g. using dfx canister --network ic metadata <canister name or id> supported_certificate_versions. In this release, the value of this metadata field value is 1,2 because certification v1 and v2 are supported.
Fixed a bug in http_request that served assets with the wrong certificate. If no encoding specified in the Accept-Encoding header is available with a certificate, an available encoding is returned without a certificate (instead of a wrong certificate, which was the case previously). Otherwise, nothing changed.
For completeness' sake, the new behavior is as follows:
- If one of the encodings specified in the
Accept-Encodingheader is available with certification, it now is served with the correct certificate. - If no requested encoding is available with certification, one of the requested encodings is returned without a certificate (instead of a wrong certificate, which was the case previously).
- If no encoding specified in the
Accept-Encodingheader is available, a certified encoding that is available is returned instead.
Added support for API versioning of the asset canister in ic-asset.
Added functionality that allows you to set asset properties during dfx deploy, even if the asset has already been deployed to a canister in the past. This eliminates the need to delete and re-deploy assets to modify properties - great news! This feature is also available when deploying assets using the --by-proposal flag. As a result, the API version of the frontend canister has been incremented from 0 to 1. The updated ic-asset version (which is what is being used during dfx deploy) will remain compatible with frontend canisters implementing both API 0 and 1. However, please note that the new frontend canister version (with API v1) will not work with tooling from before the dfx release (0.14.0).
- API version: 1
- Module hash: e7866e1949e3688a78d8d29bd63e1c13cd6bfb8fbe29444fa606a20e0b1e33f0
- #3094
- #3002
- #3065
- #3058
- #3057
- #2960
- #3051
- #3034
- #3023
- #3022
- #3021
- #3019
- #3016
- #3015
- #3001
- #2987
- #2982
Updated Motoko to 0.8.7
Updated ic-ref to 0.0.1-ca6aca90
Started bundling ic-btc-canister, release 2023-03-31
Added validate_grant_permission() and validate_revoke_permission() methods per SNS requirements.
- Module hash: 98863747bb8b1366ae5e3c5721bfe08ce6b7480fe4c3864d4fec3d9827255480
- #2958
This allows users to download SNS canister Wasm binaries.
dfx nns installhad the wrong instructions for setting up the local replica type
The permissions are as follows:
- ManagePermissions: Can grant and revoke permissions to any principal. Controllers implicitly have this permission.
- Prepare: Can call create_batch and create_chunk
- Commit: Can call commit_batch and methods that manipulate assets directly, as well as any method permitted by Prepare.
For upgraded frontend canisters, all authorized principals will be granted the Commit permission. For newly deployed frontend canisters, the initializer (first deployer of the canister) will be granted the Commit permission.
Added three new methods:
- list_permitted: lists principals with a given permission.
- Callable by anyone.
- grant_permission: grants a single permission to a principal
- Callable by Controllers and principals with the ManagePermissions permission.
- revoke_permission: removes a single permission from a principal
- Any principal can revoke its own permissions.
- Only Controllers and principals with the ManagePermissions permission can revoke the permissions of other principals.
Altered the behavior of the existing authorization-related methods to operate only on the "Commit" permission. In this way, they are backwards-compatible.
- authorize(principal): same as grant_permission(principal, Commit)
- deauthorize(principal): same as revoke_permission(permission, Commit)
- list_authorized(): same as list_permitted(Commit)
It used to be the case that any authorized principal could authorize and deauthorize any other principal. This is no longer the case. See rules above for grant_permission and revoke_permission.
- Secure HTTP headers, preventing several typical security vulnerabilities (e.g. XSS, clickjacking, and many more). For more details, see comments in
headerssection in default.ic-assets.json5. - Configures
allow_raw_accessoption in starter.ic-assets.json5config files, with the value set to its default value (which isfalse). We are showing that configuration in the default starter projects for the sake of easier discoverability, even though its value is set to the default.
By default, the frontend canister will now restrict the access of traffic to the <canister-id>.raw.ic0.app domain, and will automatically redirect all requests to the certified domain (<canister-id>.ic0.app), unless configured explicitly. Below is an example configuration to allow access to the robots.txt file from the "raw" domain:
[
{
"match": "robots.txt",
"allow_raw_access": true
}
]Important: Note that any assets already uploaded to an asset canister will be protected by this redirection, because at present the asset synchronization process does not update the allow_raw_access property, or any other properties, after creating an asset. This also applies to assets that are deployed without any configuration, and later configured to allow raw access.
At the present time, there are two ways to reconfigure an existing asset:
- re-create the asset
- delete the asset in your project's directory
- execute
dfx deploy - re-create the asset in your project's directory
- modify
.ic-assets.jsonacordingly - execute
dfx deploy
- via manual candid call
dfx canister call PROJECT_NAME_frontend set_asset_properties '( record { key="/robots.txt"; allow_raw_access=opt(opt(true)) })'
Callable only by a controller. Clears list of authorized principals and adds the caller (controller) as the only authorized principal.
effective_canister_idused forprovisional_create_canister_with_cyclesis passed as an command-line argument (defaults torwlgt-iiaaa-aaaaa-aaaaa-caiif not provided or upon parse failure)
As part of creating the support for future work, it's now possible to get and set AssetProperties for assets in frontend canister.
Similar to how this argument works in dfx canister call, this argument allows providing arguments for the request from a file.
A remote canister ID can now be specified for the __default network. If specified, dfx will assume that the canister is remote at the specified canister ID for all networks that don't have a dedicated entry.
If keyring integration is available, PEM files (except for the default identity) are now by default stored in the OS-provided keyring. If it is not available, it will fall back on the already existing password-encrypted PEM files. Plaintext PEM files are still available (e.g. for use in non-interactive situations like CI), but not recommended for use since they put the keys at risk.
To force the use of one specific storage mode, use the --storage-mode flag with either --storage-mode password-protected or --storage-mode plaintext.
This works for both dfx identity new and dfx identity import.
The flag --disable-encryption is deprecated in favour of --storage-mode plaintext. It has the same behavior.
The asset canister now has two new functions:
- Query function
list_authorizeddisplays a list of all principals that are currently authorized to change assets and the list of authorized principals. - Update function
deauthorizethat removes a principal from the list of authorized principals. It can be called by authorized principals and cotrollers of the canister.
In addition, the update function authorize has new behavior:
Now, controllers of the asset canister are always allowed to authorize new principals (including themselves).
dfx canister delete tries to withdraw as many cycles as possible from a canister before deleting it.
To do so, dfx has to manually send all cycles in the canister, minus some margin.
The margin was previously hard-coded, meaning that withdrawals can fail if the margin is not generous enough.
Now, upon failure with some margin, dfx will retry withdrawing cycles with a continuously larger margin until withdrawing succeeds or the margin becomes larger than the cycles balance.
The Motoko compiler expects all imported canisters' .did files to be in one folder when it compiles a canister.
dfx failed to organize the .did files correctly when running dfx deploy <single Motoko canister> in combintaion with the --mode reinstall flag.
There have been a few reports of people not being able to delete canisters. The error happens if the temporary wallet tries to transfer out too many cycles. The number of cycles left in the canister is bumped a little bit so that people can again reliably delete their canisters.
Updated candid to 0.8.4
- Bug fix in TS bindings
- Pretty print numbers
- Module hash: d12e4493878911c21364c550ca90b81be900ebde43e7956ae1873c51504a8757
- #2942
Updated ic-ref to master commit 3cc51be5
Updated Motoko to 0.7.6
Updated replica to elected commit b5a1a8c0e005216f2d945f538fc27163bafc3bf7. This incorporates the following executed proposals:
Updated replica to elected commit dcbf401f27d9b48354e68389c6d8293c4233b055. This incorporates the following executed proposals:
- Module hash: db07e7e24f6f8ddf53c33a610713259a7c1eb71c270b819ebd311e2d223267f0
- #2753
Allows to overwrite Content-Type, Content-Encoding, and Cache-Control HTTP headers with custom values via .ic-assets.json5 config file. Example .ic-assets.json5 file:
[
{
"match": "web-gz.data.gz",
"headers": {
"Content-Type": "application/octet-stream",
"Content-Encoding": "gzip"
}
}
]This change will trigger the update process for frontend canister (new module hash: 2ff0513123f11c57716d889ca487083fac7d94a4c9434d5879f8d0342ad9d759).
SNS canister IDs were not being parsed reliably. Now the candid file is being specified explicitly, which resolves the issue in at least some cases.
The command line interface for nns commands has been updated to:
- Give better help when the subnet type is incorrect
- Not offer --network as a flag given that it is unused
- List nns subcommands
dfx canister install and dfx deploy now have a -y flag that will automatically confirm any y/n checks made during canister installation.
The function for calling sns can now call any bundled binary.
dfx nns commands are used to deploy and manage local NNS canisters, such as:
- Governance for integration with the Internet Computer voting system
- Ledger for financial integration testing
- Internet Identity for user registration and authenttication
The asset canister now by default aliases any request to <asset> to <asset>.html or <asset>/index.html.
This can be disabled by setting the field "enable_aliasing" to false in a rule for that asset in .ic-assets.json.
This change will trigger frontend canister upgrades upon redeploying any asset canister.
Removes misleading panics when running dfx stop.
This enables easy access to toy ICP using command line tools and this key:
-----BEGIN EC PRIVATE KEY-----
MHQCAQEEICJxApEbuZznKFpV+VKACRK30i6+7u5Z13/DOl18cIC+oAcGBSuBBAAK
oUQDQgAEPas6Iag4TUx+Uop+3NhE6s3FlayFtbwdhRVjvOar0kPTfE/N8N6btRnd
74ly5xXEBNSXiENyxhEuzOZrIWMCNQ==
-----END EC PRIVATE KEY-----
For example, you can create an identity in dfx by putting this key in the file ident-1.pem and importing it:
dfx identity import ident-1 ident-1.pem
dfx --identity ident-1 ledger balance
This behavior applies to Motoko, Rust and Custom canisters. If you want to disable this behavior, you can config it in dfx.json:
"canisters" : {
"app" : {
"shrink" : false,
}
}It's now possible to define custom wasm metadata sections and their visibility in dfx.json.
At present, dfx can only add wasm metadata sections to canisters that are in wasm format. It cannot add metadata sections to compressed canisters. Since the frontend canister is now compressed, this means that at present it is not possible to add custom metadata sections to the frontend canister.
dfx no longer adds candid:service metadata to canisters of type "custom" by default. If you want dfx to add your canister's candid definition to your custom canister, you can do so like this:
"my_canister_name": {
"type": "custom",
"candid": "main.did",
"wasm": "main.wasm",
"metadata": [
{
"name": "candid:service"
}
]
},
This changelog entry doesn't go into all of the details of the possible configuration. For that, please see concepts/canister-metadata and the docs in the JSON schema.
Hyphens are not valid in shell environment variables, but do occur in canister names such as smiley-dapp. This poses a problem for vars with names such as CANISTER_ID_$\{CANISTER_NAME\}. With this change, hyphens are replaced with underscores in environment variables. The canister id of smiley-dapp will be available as CANISTER_ID_smiley_dapp. Other environment variables are unaffected.
This allows users to deploy a set of SNS canisters.
When using dfx canister install, you can now pass auto for the --mode flag, which will auto-select install or upgrade depending on need, the same way dfx deploy does. The default remains install to prevent mistakes.
dfx generate's generated bindings use network-specific canister IDs depending on the generated language, but there was previously no way to configure which network this was, so it defaulted to local. A --network flag has been added for this purpose.
There is a new command that verifies that an SNS initialization config is valid.
There is a new command that creates an sns config template.
The wasms dir path had a $ which is unwanted and now gone.
Previously the incorrect wasm canister was installed.
Previously the did files and wasms could be incompatible.
dfx start and dfx replica now ignore the --enable-canister-http parameter.
You can still disable the canister http feature through configuration:
- ~/.config/dfx/networks.json:
.local.canister_http.enabled=false - dfx.json (project-specific networks) :
.networks.local.canister_http.enabled=false
- note that dfx will report an error if a custom canister's
wasmfield is a URL and the canister also hasbuildsteps.
A developer is now able to install NNS canisters, including back end canisters such as ledger and governance, and front end canisters such as nns-dapp and internet-identity, on their local DFX server. Usage:
dfx start --clean --background
dfx nns install
This feature currently requires that the network 'local' is used and that it runs on port 8080.
The network's port can be controlled by using the field "provider" in the network's definition, e.g. by setting it to "127.0.0.1:8080".
It is now possible to set the http adapter's log level in dfx.json or in networks.json:
"http": {
"enabled": true,
"log_level": "info"
}
By default, a log level of "error" is used, in order to keep the output of a first-time dfx start minimal. Change it to "debug" for more verbose logging.
Adds an index.d.ts file to the generated declarations, allowing for better type safety in TypeScript projects.
dfx start produces a lot of log output that is at best irrelevant for most users.
Most output is no longer visible unless either --verbose is used with dfx or the relevant part's (e.g. http adapter, btc adapter, or replica) log level is changed in dfx.json or networks.json.
When creating a new identity with dfx identity new, whereas previously it would have generated an Ed25519 key, it now generates a secp256k1 key. This is to enable users to write down a BIP39-style seed phrase, to recover their key in case of emergency, which will be printed when the key is generated and can be used with a new --seed-phrase flag in dfx identity import. dfx identity import is however still capable of importing an Ed25519 key.
- Allow passing did files larger than 2KB.
- Better integration with Motoko Playground.
- SHA256 hashes of all assets are displayed when deploying the asset canister.
- A query method is added to the asset canister that returns the entire asset hash tree together with the certificate containing the certified variables of the asset canister.
See https://forum.dfinity.org/t/fixing-incorrect-compute-allocation-fee/14830
Until the rollout is complete, dfx canister update-settings --compute-allocation <N>
will fail with an error from the replica such as the following:
The Replica returned an error: code 1, message: "Canister requested a compute allocation of 1% which cannot be satisfied because the Subnet's remaining compute capacity is 0%"
Canisters that specify a remote id for the network that's getting built falsely had their build steps run, blocking some normal use patterns of dfx deploy.
Canisters with a remote id specified no longer get built.
The same applies to dfx generate.
The running replica port and url are generally useful information. Previously the code to get the URL was embedded in the network proxy code. This moves it out into a library for reuse.
Instead, the build process relies on ic-wasm to provide candid metadata for the canister, and
shrinking the canister size by stripping debug symbols and unused fuctions.
Additionally, after build step, the .wasm file is archived with gzip.
from (repository path) |
to (path in dfinity/sdk repository) |
summary |
|---|---|---|
dfinity/cdk-rs /src/ic-certified-assets |
/src/canisters/frontend/ic-certified-asset |
the core of the frontend canister |
dfinity/certified-assets / |
/src/canisters/frontend/ic-frontend-canister |
wraps ic-certified-assets to build the canister wasm |
dfinity/agent-rs /ic-asset |
/src/canisters/frontend/ic-asset |
library facilitating interactions with frontend canister (e.g. uploading or listing assets) |
dfinity/agent-rs /icx-asset |
/src/canisters/frontend/icx-asset |
CLI executable tool - wraps ic-asset |
Both .ic-assets.json and .ic-assets.json5 are valid filenames config filename, though both will get parsed
as if they were JSON5 format. Example content of the .ic-assets.json5 file:
// comment
[
{
"match": "*", // comment
/*
keys below not wrapped in quotes
*/ cache: { max_age: 999 }, // trailing comma
},
]- Learn more about JSON5: https://json5.org/
Previously existing NNS binaries were not updated regardless of the NO_CLOBBER setting.
install_canister_wasm used to fail if installing a canister not listed in dfx.json. This use case is now supported.
When running dfx start or dfx replica, the path to the dashboard page is now printed.
This is so dfx doesn't connect to a project-specific network instead of the local shared network.
In combination with the "system-wide dfx start" feature, there is a potential difference to be aware of with respect to existing projects.
Since previous versions of dfx populate dfx.json with a networks.local definition that specifies port 8000, the behavior for existing projects won't change.
However, if you've edited dfx.json and removed the networks.local definition, the behavior within the project will change: dfx will connect to the shared local network on port 4943 rather than to the project-specific network on port 8000. You would need to edit webpack.config.js to match. If you have scripts, you can run the new command dfx info webserver-port from the project directory to retrieve the port value.
By default, dfx now manages the replica process in a way that is independent of any given dfx project. We've called this feature "system-wide dfx", even though it's actually specific to your user (storing data files under $HOME), because we think it communicates the idea adequately.
The intended benefits:
- deploying dapps from separate projects alongside one another, similar to working with separate dapps on mainnet
- run
dfx startfrom any directory - run
dfx stopfrom any directory, rather than having to remember where you last randfx start
We're calling this the "shared local network." dfx start and dfx stop will manage this network when run outside any project directory, or when a project's dfx.json does not define the local network. The dfx.json template for new projects no longer defines any networks.
We recommend that you remove the local network definition from dfx.json and instead use the shared local network. As mentioned above, doing so will make dfx use port 4943 rather than port 8000.
See Local Server Configuration for details.
dfx now stores data and control files in one of three places, rather than directly under .dfx/:
.dfx/network/local(for projects in which dfx.json defines the local network)$HOME/.local/share/dfx/network/local(for the shared local network on Linux)$HOME/Library/Application Support/org.dfinity.dfx/network/local(for the shared local network on MacOS)
There is also a new configuration file: $HOME/.config/dfx/networks.json. Its schema is the same as the networks element in dfx.json. Any networks you define here will be available from any project, unless a project's dfx.json defines a network with the same name. See The Shared Local Network for the default definitions that dfx provides if this file does not exist or does not define a local network.
This displays the port that the icx-proxy process listens on, meaning the port to connect to with curl or from a web browser.
This displays the listening port of the replica.
This displays the revision of the replica bundled with dfx, which is the same revision referenced in replica election governance proposals.
This displays the path to your user's networks.json file where all networks are defined.
greet method was marked as an update call, but it performs no state updates. Changing it to query call will result in faster execution.
The dfx schema command can now display the schema for either dfx.json or for networks.json. By default, it still displays the schema for dfx.json.
dfx schema --for networksIf you have a pre-initialized agent in your JS code, you can now pass it to createActor's options. Conflicts with the agentOptions config - if you pass both the agent option will be used and you will receive a warning.
const plugActor = createActor(canisterId, {
agent: plugAgent
})Users can now specify node_compatibility: true in declarations. The flag introduces node.js enhancements, which include importing isomorphic-fetch and configuring the default actor with isomorphic-fetch and host.
// dfx.json
"declarations": {
"output": "src/declarations",
"node_compatibility": true
}DFX new template now uses dfx generate instead of rsync. Adds deprecation warning to index.js in .dfx/<network-name>/<canister-name> encouringing developers to migrate to the dfx generate command instead. If you have a package.json file that uses rsync from .dfx, consider switching to something like this:
"scripts": {
"build": "webpack",
"prebuild": "npm run generate",
"start": "webpack serve --mode development --env development",
"prestart": "npm run generate",
// It's faster to only generate canisters you depend on, omitting the frontend canister
"generate": "dfx generate hello_backend"
},Using dfx wallet --network ic redeem-faucet-coupon <my coupon> faucet users have a much easier time to redeem their codes.
If the active identity has no wallet configured, the faucet supplies a wallet to the user that this command will automatically configure.
If the active identity has a wallet configured already, the faucet will top up the existing wallet.
Alternative faucets can be used, assuming they follow the same interface. To direct dfx to a different faucet, use the --faucet <alternative faucet id> flag.
The expected interface looks like the following candid functions:
redeem: (text) -> (principal);
redeem_to_wallet: (text, principal) -> (nat);
The function redeem takes a coupon code and returns the principal to an already-installed wallet that is controlled by the identity that called the function.
The function redeem_to_wallet takes a coupon code and a wallet (or any other canister) principal, deposits the cycles into that canister and returns how many cycles were deposited.
By default, if dfx is not running on the ic (or networks with a different name but the same configuration), it will automatically create a cycles wallet in case it hasn't been created yet.
It is now possible to inhibit automatic wallet creation by setting the DFX_DISABLE_AUTO_WALLET environment variable.
When installing a new Wasm module to a canister, DFX will now wait for the updated state (i.e. the new module hash) to be visible in the replica's certified state tree before proceeding with post-installation tasks or producing a success status.
dfx config has been removed. Please update Bash scripts to use jq, PowerShell scripts to use ConvertTo-Json, nushell scripts to use to json, etc.
Command flags have been moved to a more traditional location; they are no longer positioned per subcommand, but instead are able to be all positioned after the final subcommand. In prior versions, a command might look like:
dfx --identity alice canister --network ic --wallet "$WALLET" create --allThis command can now be written:
dfx canister create --all --network ic --wallet "$WALLET" --identity aliceThe old syntax is still available, though, so you don't need to migrate your scripts.
When using dfx canister update-settings, it is easy to mistake --controller for --add-controller. For this reason --controller has been renamed to --set-controller.
This is a breaking change. The only thing this was still serving was the /_/candid endpoint. If you need to retrieve the candid interface for a local canister, you can use dfx canister metadata <canister> candid:service.
- if there is no wallet to upgrade
- if trying to upgrade a local wallet from outside of a project directory
Canister creation fee was calculated with 1T cycles instead of 0.1T.
When dfx deploy and dfx canister install upgrade a canister, they ensure that the new candid interface is compatible with the previous candid interface. They write a file with extension .old.did that contains the previous interface. In some circumstances these files could be written in the project directory. dfx now always writes them under the .dfx/ directory.
This fixes the following error:
> dfx canister install --wasm ~/counter.wasm eop7r-riaaa-aaaak-qasxq-cai
Error: Failed while determining if canister 'eop7r-riaaa-aaaak-qasxq-cai' is remote on network 'ic'.
Caused by: Failed while determining if canister 'eop7r-riaaa-aaaak-qasxq-cai' is remote on network 'ic'.
Failed to figure out if canister 'eop7r-riaaa-aaaak-qasxq-cai' has a remote id on network 'ic'.
Invalid argument: Canister eop7r-riaaa-aaaak-qasxq-cai not found in dfx.jsonIt is now possible to specify the replica's log level. Possible values are critical, error, warning, info, debug, and trace.
The log level defaults to the level 'error'. Debug prints (e.g. Debug.print("...") in Motoko) still show up in the console.
The log level can be specified in the following places (See system-wide dfx start for more detailed explanations on the network types):
- In file
networks.jsonin the field<network name>.replica.log_levelfor shared networks. - In file
dfx.jsonin the fieldnetworks.<network name>.replica.log_levelfor project-specific networks. - In file
dfx.jsonin the fielddefaults.replica.log_levelfor project-specific networks. Requires a project-specific network to be run, otherwise this will have no effect.
Canister sandboxing is enabled to be consistent with the mainnet.
It is now possible to do e.g. dfx ledger account-id --of-canister fg7gi-vyaaa-aaaal-qadca-cai as well as dfx ledger account-id --of-canister my_canister_name when checking the ledger account id of a canister.
Previously, dfx only accepted canister aliases and produced an error message that was hard to understand.
Motivated by this forum post.
It is still possible to pin the dfx version by adding "dfx":"<dfx version to pin to>" to a project's dfx.json.
The prompt for entering your passphrase in order to decrypt an identity password read: "Please enter a passphrase for your identity" However, at that point, it isn't "a" passphrase. It's either your passphrase, or incorrect. Changed the text in this case to read: "Please enter the passphrase for your identity"
dfx ledger create-canister gets a new option --subnet-type that allows users to choose a type of subnet that their canister can be created on. Additionally, a dfx ledger show-subnet-types is introduced which allows to list the available subnet types.
Updated replica to release candidate 93dcf2a2026c34330c76149dd713d89e37daa533.
This also incorporates the following executed proposals:
- 85007
- 84391
- 83786
- 82425
- 81788
- 81571
- 80992
- 79816
- 78693
- 77589
- 76228
- 75700
- 75109
- 74395
- 73959
- 73714
- 73368
- 72764
Updated ic-ref to 0.0.1-1fba03ee
- introduce awaitKnown
- trivial implementation of idle_cycles_burned_per_day
- Module hash: b944b1e5533064d12e951621d5045d5291bcfd8cf9d60c28fef02c8fdb68e783
- https://github.com/dfinity/cycles-wallet/commit/fa86dd3a65b2509ca1e0c2bb9d7d4c5be95de378
- Module hash: 6c8f7a094060b096c35e4c4499551e7a8a29ee0f86c456e521c09480ebbaa8ab
- #2720
The feature is not yet implemented on icx-proxy-level, and is causing 500 HTTP response for some type of assets every second request.
fix: dfx now only adds candid:service metadata to custom canisters that have at least one build step
This way, if a canister uses a premade canister wasm, dfx will use it as-is.
It is now possible to develop multiple-canister projects using the Motoko VSCode extension.
Patches a JavaScript language binding compatibility issue encountered in web browsers which do not support the (?.) operator.
dfx is now capable of displaying the schema for dfx.json. You can see the schema by running dfx schema or write the schema to a file with dfx schema --outfile path/to/file/schema.json.
- The
.ic-assets.jsonfile should be placed inside directory with assets, or its subdirectories. Multiple config files can be used (nested in subdirectories). Example of.ic-assets.jsonfile format:
[
{
"match": ".*",
"cache": {
"max_age": 20
},
"headers": {
"X-Content-Type-Options": "nosniff"
},
"ignore": false
},
{
"match": "**/*",
"headers": null
},
{
"match": "file.json",
"ignore": true
}
]-
Configuring assets works only during asset creation - any changes to
.ic-assets.jsonfiles won't have any effect effect for assets that have already been created. We are working on follow up implementation with improvements to handle updating these properties. -
headersfrom multiple applicable rules are being stacked/concatenated, unlessnullis specified, which resets/empties the headers. -
Both
"headers": {}and absence ofheadersfield don't have any effect on end result. -
Valid JSON format is required, i.e. the array of maps,
matchfield is required. Only the following fields are accepted:cache,ignore,headers,match. The glob pattern has to be valid. -
The way matching rules work:
- The most deeply nested config file takes precedence over the one in parent dir. In other words, properties from a rule matching a file in a subdirectory override properties from a rule matching a file in a parent directory
- Order of rules within file matters - last rule in config file takes precedence over the first one
-
The way
ignorefield works:- By default, files that begin with a
.are ignored, while all other files are included. - The
.ignorefield overrides this, if present. - If a directory is ignored, file and directories within it cannot be un-ignored.
- A file can be ignored and un-ignored many times, as long as any of its parent directories haven't been ignored.
- By default, files that begin with a
A longstanding bug with dfx deploy is that if an installation is skipped (usually an implicitly included dependency), it still requires arguments even if the installed canister doesn't. As of this release that bug is now fixed.
Configures the replica to emit additional logging from the bitcoin canister whenever the bitcoin feature is enabled. This helps show useful information to developers, such as the bitcoin height that the replica currently sees.
Prior to 0.11.0, a custom canister's build field could be left off if dfx build was never invoked. To aid in deploying prebuilt canisters, this behavior is now formalized; omitting build is equivalent to build: [].
dfx build, in Rust canisters, now uses the --locked flag when building with Cargo. To offset this, dfx new --type rust now runs cargo update on the resulting project.
ECDSA signature signing is now enabled by default in new projects, or by running dfx start --clean.
A test key id "Secp256k1:dfx_test_key" is ready to be used by locally created canisters.
Updated replica to elected commit 6e86169e98904047833ba6133e5413d2758d90eb. This incorporates the following executed proposals:
The names of canisters created for new projects have changed.
After dfx new <project>, the canister names are:
<project>_backend(previously<project>)<project>_frontend(previously<project>_assets)
For example, to query a canister's candid service definition: dfx canister metadata hello_backend candid:service
The dfx internal webserver now only services the /_/candid endpoint. This
is now deprecated. If you were using this to query candid definitions, you
can instead use dfx canister metadata.
Optimize Rust canister Wasm module via ic-wasm library instead of ic-cdk-optimizer. A separate installation of ic-cdk-optimizer is no longer needed.
The actual optimization was kept the same.
Enables passing large arguments that cannot be passed directly in the command line using the --argument-file flag. For example:
- Named file:
dfx canister call --argument-file ./my/argument/file.txt my_canister_name greet - Stdin:
echo '( null )' | dfx canister call --argument-file - my_canister_name greet
A lower threshold was no longer necessary.
The bitcoin adapter's logging can be very verbose if debug logging is enabled, making it difficult to make sense of what's going on. On the other hand, these logs are useful for triaging problems.
To get the best of both worlds, this release adds support for an additional configuration option in dfx.json:
"bitcoin": {
"enabled": true,
"nodes": ["127.0.0.1:18444"],
"log_level": "info" <------- users can now configure the log level
}
By default, a log level of "info" is used, which is relatively quiet. Users can change it to "debug" for more verbose logging.
This includes the following changes:
- Fetch did file from canister metadata
- Better flamegraph support
- Fix bigint error for vec nat8 type
After dfx start --host 127.0.0.1:0, the dfx webserver will listen on an ephemeral port. It stores the port value in .dfx/webserver-port. dfx will now look for this file, and if a port is contained within, use that port to connect to the dfx webserver.
Running dfx deploy, dfx canister id, dfx canister call and so forth work as expected
if run from within any subdirectory of a dfx project. Previously, this would create
canister_ids.json or .dfx/local/canister_ids.json within the subdirectory.
You can now add your own custom post-installation/post-deployment tasks to any canister type. The new post-install key for canister objects in dfx.json can be a command or list of commands, similar to the build key of custom canisters, and receives all the same environment variables. For example, to replicate the upload task performed with assets canisters, you might set "post-install": "icx-asset sync $CANISTER_ID dist".
Assets are now uploaded directly from their source directories, rather than first being copied to an output directory.
If you're using dfx deploy, you won't see any change in functionality. If you're running
dfx canister install --mode=upgrade, changed files in asset source directories will
be detected and uploaded even without an intervening dfx build.
The environment variable format CANISTER_CANDID_{name}, used in Rust projects, was deprecated in 0.9.2, to be unified with the variables CANISTER_CANDID_PATH_{name} which are used in other project types. It has now been removed. Note that you will need to update ic-cdk-macros if you use the #[import] macro.
The dfx config command has several issues and is ultimately a poor replacement for jq. The command is being deprecated, and will be removed in a later release; we recommend switching to jq or similar tools (e.g. ConvertTo-Json in PowerShell, to json in nushell, etc.)
Build scripts now always receive a CWD of the DFX project root, instead of wherever dfx was invoked from, and a bare script script.sh can be specified without needing to prefix with ./.
Motoko canisters already included this metadata.
Also added this metadata to the asset canister wasm, which will cause the next deploy to install this new version.
Some developers mistakenly think that the freezing threshold is measured in cycles, but it is actually measured in seconds. To stop them from accidentally freezing their canisters, setting a freezing threshold above 50M seconds (~1.5 years) now requires a confirmation.
Resolves an issue where webpack-cli was was breaking when users tried to run npm start in a fresh project. For affected users of 0.10.1, you can resolve this issue manually by running npm install webpack@latest webpack-cli@latest terser-webpack-plugin@latest.
Ledger 7424ea8 deprecates the existing notify function with a switch parameter between creating and topping up a canister, and introduces two
functions for doing the same. This should mostly be invisible to users, except that previously, if dfx ledger create-canister or dfx ledger top-up
failed, you would call dfx ledger notify after correcting the issue. In order to support the change, this command has been changed to two subcommands:
dfx ledger notify create-canister and dfx ledger notify top-up.
Previously, the ledger commands assumed all transfers were made from the default subaccount for the identity principal. This feature adds a --from-subaccount flag to dfx ledger transfer, dfx ledger create-canister, and dfx ledger top-up, to enable making transfers from a selected subaccount. A --subaccount flag is also added to dfx ledger balance for convenience. Subaccounts are expected as 64-character hex-strings (i.e. 32 bytes).
When a canister with type rust is built and cargo-audit is installed, dfx will now check for vulnerabilities in the dependencies. If a vulnerability is found, dfx will recommend that the user update to a version without known vulnerabilities.
Calls made to retrieve the help output for canister update-settings was missing the freezing-threshold parameter.
WARN and ERROR messages are now clearly labelled as such, and the labels are colored accordingly.
This is now included when running dfx canister update-settings -h.
There is no real reason for dfx schema to not work when a broken dfx.json is in the current folder - this is actually a very common scenario when dfx schema gets used.
The candid file specified in the field canisters.<canister name>.candid of dfx.json, or if that not exists canisters.<canister name>.remote.candid, is now used when running dfx canister call, even when dfx fails to determine the canister type.
After running dfx start --enable-bitcoin twice in a row (stopping dfx in between), the second
launched replica would fail to connect to the btc adapter. This is because ic-starter
does not write a new configuration file if one already exists, so the configuration file
used by the replica referred to one socket path, while dfx passed a different socket path
to the btc adapter.
Now dfx reuses the previously-used unix domain socket path, for both the btc adapter and for the canister http adapter.
Previously, dfx stop would send the TERM signal to the running dfx and its child processes,
and then exit immediately.
This avoids interference between a dfx process performing cleanup at shutdown and a dfx process that is starting.
dfx ping now uses the anonymous identity, and no longer requires dfx.json to be present.
When the bitcoin feature is enabled, dfx was launching the replica with the "bitcoin_testnet" feature. The correct feature to use is "bitcoin_regtest".
dfx replica writes the port of the running replica to one of these locations:
- .dfx/replica-configuration/replica-1.port
- .dfx/ic-ref.port
dfx bootstrap will now use this port value, so it's no longer necessary to edit dfx.json after running dfx replica.
In dfx.json, the bootstrap, bitcoin, canister_http, and replica settings can
now be specified on the local network, rather than in the defaults field.
If one of these four fields is set for the local network, the corresponding field
in defaults will be ignored.
Example:
{
"networks": {
"local": {
"bind": "127.0.0.1:8000",
"canister_http": {
"enabled": true
}
}
}
}Updated agent-rs to 0.18.0
Updated Motoko from 0.6.28 to 0.6.29.
Updated replica to elected commit 8993849de5fab76e796d67750facee55a0bf6649. This incorporates the following executed proposals:
Updated ic-ref to 0.0.1-173cbe84
- add ic0.performance_counter system interface
- add system API for ECDSA signing
- allow optional "error_code" field in responses
- support gzip-compressed canister modules
- enable canisters to send HTTP requests
Dfx already points to the asset canister's assets directory, and copying to disk could sometimes lead to an annoying "too many open files" error.
On Linux, dfx 0.10.0 failed any operation with an HSM with the following error:
Error: IO: Dynamic loading not supported
The fix was to once again dynamically-link the Linux build.
Dfx is now capable of providing explanations and remediation suggestions for entire categories of errors at a time.
Explanations and suggestions will slowly be added over time.
To see an example of an already existing suggestion, run dfx deploy --network ic while using an identity that has no wallet configured.
Most errors that happen within dfx are now reported in much more detail. No more plain File not found without explanation what even was attempted.
fix: identities with configured wallets are not broken anymore and removed only when using the --drop-wallets flag
When an identity has a configured wallet, dfx no longer breaks the identity without actually removing it. Instead, if the --drop-wallets flag is specified, it properly removes everything and logs what wallets were linked, and when the flag is not specified, it does not remove anything.
The behavior for identities without any configured wallets is unchanged.
dfx command-line parameters for bitcoin integration:
dfx start --enable-bitcoin # use default node 127.0.0.1:18444
dfx start --enable-bitcoin --bitcoin-node <node>The above examples also work for dfx replica.
These default to values from dfx.json:
.defaults.bitcoin.nodes
.defaults.bitcoin.enabled
The --bitcoin-node parameter, if specified on the command line, implies --enable-bitcoin.
If --enable-bitcoin or .defaults.bitcoin.enabled is set, then dfx start/replica will launch the ic-btc-adapter process and configure the replica to communicate with it.
Default behaviour changed for dfx wallet balance, it will now print cycles amount upscaled to trillions.
New flag --precise added to dfx wallet balance. Allows to get exact amount of cycles in wallet (without upscaling).
dfx command-line parameters for canister http requests integration:
dfx start --enable-canister-http
dfx replica --enable-canister-http
This defaults to the following value in dfx.json:
.defaults.canister_http.enabled
Specifying the network provider as https://ic0.app/ instead of https://ic0.app is now recognised as the real IC network.
Added ic-canister-http-adapter to the binary cache.
Updated Motoko from 0.6.26 to 0.6.28.
Updated replica to elected commit b90edb9897718730f65e92eb4ff6057b1b25f766. This incorporates the following executed proposals:
Updated icx-proxy to commit c312760a62b20931431ba45e5b0168ee79ea5cda
- Added gzip and deflate body decoding before certification validation.
- Fixed unzip and streaming bugs
- Added Prometheus metrics endpoint
- Added root and invalid ssl and dns mapping
Before this, deploying a canister with an opt Foo init argument without specifying an --argument would lead to an error:
$ dfx deploy
Error: Invalid data: Expected arguments but found none.With this change, this isn't an error anymore, but instead null is passed as a value. In general, if the user does not provide an --argument, and if the init method expects only opt arguments, then dfx will supply null for each argument.
Note in particular that this does not try to match opt arguments for heterogeneous (opt/non-opt) signatures. Note moreover that this only impacts a case that would previously error out, so no existing (working) workflows should be affected.
This check was previously performed on local networks, but not on mainnet.
Allows one to provide the .did file for calls to an arbitrary canister.
You no longer need a DFX project setup with a build task to install an already-built wasm module into a canister ID. The new --wasm <path> flag to dfx canister install will bypass project configuration and install the wasm module at <path>. A DFX project setup is still recommended for general use; this should mostly be used for installing pre-built canisters. Note that DFX will also not perform its usual checks for API/ABI/stable-memory compatibility in this mode.
Cycle counts can now exceed the previously set maximum of 2^64. The new limit is 2^128. A new wallet version has been bundled with this release that supports the new cycle count. You will not be able to use this feature with your existing wallets without running dfx wallet upgrade, but old wallets will still work just fine with old cycle counts.
dfx will once again display 'dfx is already running' if dfx is already running, rather than 'Address already in use'.
As a consequence, after dfx start failed to notice that dfx was already running,
it would replace .dfx/pid with an empty file. Later invocations of dfx stop
would display no output and return a successful exit code, but leave dfx running.
fix: dfx canister update-settings <canister id> works even if the canister id is not known to the project.
This makes the behavior match the usage text of the command:
<CANISTER> Specifies the canister name or id to update. You must specify either canister name/id or the --all option
When upgrading a canister, dfx deploy and dfx canister install skip installing the .wasm
if the wasm hash did not change. This avoids a round trip through stable memory for all
assets on every dfx deploy, for example. By passing this argument, dfx will instead
install the wasm even if its hash matches the already-installed wasm.
A new environment variable, DFX_CACHE_ROOT, has been introduced to allow setting the cache root directory to a different location than the configuration root directory. Previously DFX_CONFIG_ROOT was repurposed for this which only allowed one location to be set for both the cache and configuration root directories.
This is a breaking change since setting DFX_CONFIG_ROOT will no longer set the cache root directory to that location.
Previously, dfx canister call --with-cycles 1 would silently ignore the --with-cycles argument as the DFX principal has no way to pass cycles and the call must be forwarded through the wallet. Now it will error instead of silently ignoring it. To forward a call through the wallet, use --wallet $(dfx identity get-wallet), or --wallet $(dfx identity --network ic get-wallet) for mainnet.
The local replica sets its parameters according to the subnet type defined in defaults.replica.subnet_type, defaulting to 'application' when none is specified.
This makes it less likely to accidentally hit the 'cycles limit exceeded' error in production. Since the previous default was system, you may see these types errors in development instead.
Possible values for defaults.replica.subnet_type are: "application", "verifiedapplication", "system"
Example how to specify the subnet type:
{
"defaults": {
"replica": {
"subnet_type": "verifiedapplication"
}
}
}dfx ledger fabricate-cycles <canister (id)> <optional amount> can be used during local development to create cycles out of thin air and add them to a canister. Instead of supplying a canister name or id it is also possible to use --all to add the cycles to every canister in the current project. When no amount is supplied, the command uses 10T cycles as default. Using this command with --network ic will result in an error.
dfx identity new and dfx identity import now ask you for a password to encrypt the private key (PEM file) when it is stored on disk.
If you decide to use a password, your key will never be written to disk in plain text.
In case you don't want to enter your password all the time and want to take the risk of storing your private key in plain text, you can use the --disable-encryption flag.
The default identity as well as already existing identities will NOT be encrypted. If you want to encrypt an existing identity, use the following commands:
dfx identity export identity_name > identity.pem
# if you have set old_identity_name as the identity that is used by default, switch to a different one
dfx identity use other_identity
dfx identity remove identity_name
dfx identity import identity_name identity.pemIf you want to get your identity out of dfx, you can use dfx identity export identityname > exported_identity.pem. But be careful with storing this file as it is not protected with your password.
If you want to script identity creation and don't care about overwriting existing identities, you now can use the --force flag for the commands dfx identity new and dfx identity import.
When running dfx deploy --network ic, dfx canister --network ic create, or dfx identity --network ic get-wallet dfx no longer automatically creates a cycles wallet for the user if none is configured. Instead, it will simply report that no wallet was found for that user.
Dfx still creates the wallet automatically when running on a local network, so the typical workflow of dfx start --clean and dfx deploy will still work without having to manually create the wallet.
When something went wrong during identity creation, the identity was not listed as existing. But when trying to create an identity with that name, it was considered to be already existing.
Added command-line parameters:
dfx start --enable-bitcoin --btc-adapter-config <path>
dfx replica --enable-bitcoin --btc-adapter-config <path>These default to values from dfx.json:
.defaults.bitcoin.btc_adapter_config
.defaults.bitcoin.enabled
The --btc-adapter-config parameter, if specified on the command line, implies --enable-bitcoin.
If --enable-bitcoin or .defaults.bitcoin.enabled is set, and a btc adapter configuration is specified, then dfx start/replica will launch the ic-btc-adapter process.
This integration is not yet complete, pending upcoming functionality in ic-starter.
dfx now displays the context of an error in several places where previously the only error message would be something like "No such file or directory."
Webpack dev server now works for Node 18 (and should work for Node 17). A few packages are also upgraded
Updated to version 0.14.0 of agent-rs
- Module hash: bb001d1ebff044ba43c060956859f614963d05c77bd778468fce4de095fe8f92
- https://github.com/dfinity/cycles-wallet/commit/f18e9f5c2f96e9807b6f149c975e25638cc3356b
Updated replica to elected commit b3788091fbdb8bed7e527d2df4cc5e50312f476c. This incorporates the following executed proposals:
Added the ic-btc-adapter binary to the cache.
Updated Motoko from 0.6.25 to 0.6.26.
In preparation for BTC integration, added configuration for the bitcoind port:
{
"canisters": {},
"defaults": {
"bitcoind": {
"port": 18333
}
}
}Updated icx-proxy to commit 594b6c81cde6da4e08faee8aa8e5a2e6ae815602, now static-linked.
- upgrade HTTP calls upon canister request
- no longer proxies /_/raw to the dfx internal webserver
- allows for generic StreamingCallback tokens
Updated replica to blessed commit d004accc3904e24dddb13a11d93451523e1a8a5f. This incorporates the following executed proposals:
Updated Motoko from 0.6.21 to 0.6.25.
Newly deployed Motoko canisters now embed the Candid interface and Motoko stable signatures in the Wasm module.
dfx deploy and dfx canister install will automatically check
1) the backward compatible of Candid interface in both upgrade and reinstall mode;
2) the type safety of Motoko stable variable type in upgrade mode to avoid accidentally lossing data;
See Upgrade compatibility for more details.
The three canister types that use a custom build tool - assets, rust, and custom - now all support the same set of environment variables during the build task:
DFX_VERSION- The version of DFX that was used to build the canister.DFX_NETWORK- The network name being built for. Usuallyicorlocal.CANISTER_ID_{canister}- The canister principal ID of the canister{canister}registered indfx.json.CANISTER_CANDID_PATH_{canister}- The path to the Candid interface file for the canister{canister}among your canister's dependencies.CANISTER_CANDID_{canister}(deprecated) - the same asCANISTER_CANDID_PATH_{canister}. This is provided for backwards compatibility withrustandcustomcanisters, and will be removed in dfx 0.10.0.CANISTER_ID- Same asCANISTER_ID_{self}, where{self}is the name of this canister.CANISTER_CANDID_PATH- Same asCANISTER_CANDID_PATH_{self}, where{self}is the name of this canister.
If you have an installation of the ICP Ledger (see Ledger Installation Guide), dfx ledger balance and dfx ledger transfer now support
--ledger-canister-id parameter.
Some examples:
$ dfx ledger \
--network local \
balance \
--ledger-canister-id rrkah-fqaaa-aaaaa-aaaaq-cai
1000.00000000 ICP
$ dfx ledger \
--network local \
transfer --amount 0.1 --memo 0 \
--ledger-canister-id rrkah-fqaaa-aaaaa-aaaaq-cai 8af54f1fa09faeca18d294e0787346264f9f1d6189ed20ff14f029a160b787e8
Transfer sent at block height: 1The dfx ledger account-id can now compute addresses of principals and canisters.
The command also supports ledger subaccounts now.
dfx ledger account-id --of-principal 53zcu-tiaaa-aaaaa-qaaba-cai
dfx ledger --network small02 account-id --of-canister ledger_demo
dfx ledger account-id --of-principal 53zcu-tiaaa-aaaaa-qaaba-cai --subaccount 0000000000000000000000000000000000000000000000000000000000000001All dfx commands will now print the full stack of errors that led to the problem, not just the most recent error.
Example:
Error: Subaccount '00000000000000000000000000000000000000000000000000000000000000000' is not a valid hex string
Caused by:
Odd number of digits
quill generate currently outputs .pem files without an EC PARAMETERS section.
dfx identity import will now correctly identify these as EC keys, rather than Ed25519.
dfx now calls transfer rather than send_dfx, and sets the created_at_time field in order to retry the following commands:
- dfx ledger create-canister
- dfx ledger top-up
- dfx ledger transfer
It's now possible to specify that a canister in dfx.json references a "remote" canister on a specific network, that is, a canister that already exists on that network and is managed by some other project.
Motoko, Rust, and custom canisters may be configured in this way.
This is the general format of the configuration in dfx.json:
{
"canisters": {
"<canister name>": {
"remote": {
"candid": "<path to candid file to use when building on remote networks>",
"id": {
"<network name>": "<principal on network>"
}
}
}
}
}The "id" field, if set for a given network, specifies the canister ID for the canister on that network. The canister will not be created or installed on these remote networks. For other networks, the canister will be created and installed as usual.
The "candid" field, if set within the remote object, specifies the candid file to build against when building other canisters on a network for which the canister is remote. This definition can differ from the candid definitions for local builds.
For example, if have an installation of the ICP Ledger (see Ledger Installation Guide)
in your dfx.json, you could configure the canister ID of the Ledger canister on the ic network as below. In this case,
the private interfaces would be available for local builds, but only the public interfaces would be available
when building for --network ic.
{
"canisters": {
"ledger": {
"type": "custom",
"wasm": "ledger.wasm",
"candid": "ledger.private.did",
"remote": {
"candid": "ledger.public.did",
"id": {
"ic": "ryjl3-tyaaa-aaaaa-aaaba-cai"
}
}
},
"app": {
"type": "motoko",
"main": "src/app/main.mo",
"dependencies": [ "ledger" ]
}
}
}As a second example, suppose that you wanted to write a mock of the ledger in Motoko.
In this case, since the candid definition is provided for remote networks,
dfx build (with implicit --network local) will build app against the candid
definitions defined by mock.mo, but dfx build --network ic will build app against
ledger.public.did.
This way, you can define public update/query functions to aid in local testing, but
when building/deploying to mainnet, references to methods not found in ledger.public.did
will be reports as compilation errors.
{
"canisters": {
"ledger": {
"type": "motoko",
"main": "src/ledger/mock.mo",
"remote": {
"candid": "ledger.public.did",
"id": {
"ic": "ryjl3-tyaaa-aaaaa-aaaba-cai"
}
}
},
"app": {
"type": "motoko",
"main": "src/app/main.mo",
"dependencies": [ "ledger" ]
}
}
}It's now possible to generate the interface of a remote canister using a .did file using the dfx remote generate-binding <canister name>|--all command. This makes it easier to write mocks for local development.
Currently, dfx can generate .mo, .rs, .ts, and .js bindings.
This is how you specify how to generate the bindings in dfx.json:
{
"canisters": {
"<canister name>": {
"main": "<path to mo/rs/ts/js file that will be generated>",
"remote": {
"candid": "<path to candid file to use when generating bindings>"
"id": {}
}
}
}
}Upgraded from a432156f24faa16d387c9d36815f7ddc5d50e09f to ab8e3f5a04f0f061b8157c2889f8f5de05f952bb
- Support 128-bit system api for cycles
- Include canister_ranges in the state tree
- Removed limit on cycles in a canister
Updated replica to blessed commit 04fe8b0a1262f07c0cec1fdfa838a37607370a61. This incorporates the following executed proposals:
Updated Motoko from 0.6.20 to 0.6.21.
Breaking change: Canister commands, except for dfx canister create, will make the call directly, rather than via the user's wallet. The --no-wallet flag is thus removed from dfx canister as its behavior is the default.
When working with existing canisters, use the --wallet flag in conjunction with dfx identity get-wallet in order to restore the old behavior.
You will need to upgrade your wallet and each of your existing canisters to work with the new system. To do so, execute the following in each of your dfx projects:
dfx wallet upgrade
dfx canister --wallet "$(dfx identity get-wallet)" update-settings --all --add-controller "$(dfx identity get-principal)"To upgrade projects that you have deployed to the IC mainnet, execute the following:
dfx wallet --network ic upgrade
dfx canister --network ic --wallet "$(dfx identity --network ic get-wallet)" update-settings --all --add-controller "$(dfx identity get-principal)"dfx canister update-settings previously only let you overwrite the entire controller list; --add-controller and --remove-controller instead add or remove from the list.
dfx canister delete --no-withdrawal <canister> can be used to delete a canister without attempting to withdraw cycles.
This matches the value used in production and is meant to exceed the configured 5 MB wasmtime stack.
Fixed a defect in asset synchronization where no retries would be attempted after the first 30 seconds overall.
Updated Motoko from 0.6.11 to 0.6.20.
- Implement type union/intersection
- Transform for-loops on arrays into while-loops
- Tighten typing rules for type annotations in patterns
- Candid decoding: skip vec any fast
- Bump up MAX_HP_FOR_GC from 1GB to 3GB
- Candid decoder: Trap if a principal value is too large
- Eliminate bignum calls from for-iteration on arrays
- Improve scheduling
- Improve performance of bignum equality
- Stable signatures: frontend, metadata, command-line args
- Added heartbeat support
- Module hash: 53ec1b030f1891bf8fd3877773b15e66ca040da539412cc763ff4ebcaf4507c5
- https://github.com/dfinity/cycles-wallet/commit/57e53fcb679d1ea33cc713d2c0c24fc5848a9759
Updated replica to blessed commit 75138bbf11e201aac47266f07bee289dc18a082b. This incorporates the following executed proposals:
You can now declare "rust" canisters in dfx.json.
{
"canisters": {
"canister_name": {
"type": "rust",
"package": "crate_name",
"candid": "path/to/canister_name.did"
}
}
}Don't forget to place a Cargo.toml in your project root.
Then dfx will build the rust canister with your rust toolchain.
Please also make sure that you have added the WebAssembly compilation target.
rustup target add wasm32-unknown-unknownYou can also create new dfx project with a default rust canister.
dfx new --type=rust <project-name>Updates dependencies to latest for Webpack, and updates config. Additionally simplifies environment variables for canister ID's in config.
Additionally adds some polish to the starter template, including a favicon and using more semantic html in the example app
You can now override the location of any executable normally called from the cache by specifying
an environment variable. For example, DFX_ICX_PROXY_PATH will specify the path for icx-proxy.
dfx deploy can now reinstall a single canister, controlled by a new --mode=reinstall parameter.
This is destructive (it resets the state of the canister), so it requires a confirmation
and can only be performed on a single canister at a time.
dfx canister install --mode=reinstall <canister> also requires the same confirmation,
and no longer works with --all.
The included replica now supports canister_heartbeat. This only works with rust canisters for the time being,
and does not work with the emulator (dfx start --emulator).
This means dfx start --emulator has a chance of working if nix is not installed.
This has always been broken, even before dfx 0.7.0.
This means dfx start will work again on linux. This bug was introduced in dfx 0.8.2.
The --no-artificial-delay option not being the default has been causing a lot of confusion.
Now that we have measured in production and already applied a default of 600ms to most subnets deployed out there,
we have set the same default for dfx and removed the option.
Updated Motoko from 0.6.10 to 0.6.11.
- Assertion error messages are now reproducible (#2821)
By default dfx canister delete will return cycles to the default cycles wallet.
Cycles can be returned to a designated canister with --withdraw-cycles-to-canister and
cycles can be returned to dank at the current identity principal with --withdraw-cycles-to-dank
and to a designated principal with --withdraw-cycles-to-dank-principal.
It is now possible to create canisters with more than one controller by
passing multiple instances of the --controller parameter to dfx canister create`.
You will need to upgrade your wallet with dfx wallet upgrade, or dfx wallet --network ic upgrade
It is now possible to configure a canister to have more than one controller by
passing multiple instances of the --controller parameter to dfx canister update-settings`.
Breaking change: The controller parameter for dfx canister create is now passed as a named parameter,
rather than optionally following the canister name.
Old: dfx canister create [canister name] [controller]
New: dfx canister create --controller <controller> [canister name]
Previously this would always look in $HOME/.dfinity/identity/creds.pem.
Updated the maximum value for the --memory-allocation value to be 12 GiB (12,884,901,888 bytes)
- Module hash: 9183a38dd2eb1a4295f360990f87e67aa006f225910ab14880748e091248e086
- https://github.com/dfinity/cycles-wallet/commit/9ef38bb7cd0fe17cda749bf8e9bbec5723da0e95
You will need to upgrade your wallet with dfx wallet upgrade, or dfx wallet --network ic upgrade
The included replica now supports public spec 0.18.0
- Canisters can now have more than one controller
- Adds support for 64-bit stable memory
- The replica now goes through an initialization sequence, reported in its status
as
replica_health_status. Until this reports ashealthy, queries or updates will fail. **dfx start --backgroundwaits to exit untilreplica_health_statusishealthy. ** If you rundfx startwithout--background, you can calldfx ping --wait-healthyto wait until the replica is healthy.
Updated Motoko from 0.6.7 to 0.6.10
- add Debug.trap : Text -> None (motoko-base #288)
- Introduce primitives for
Int⇔Floatconversions (#2733) - Fix crashing bug for formatting huge floats (#2737)
dfx generateThis new command will generate type declarations for canisters in dfx.json.
You can control what will be generated and how with corresponding configuration in dfx.json.
Under dfx.json → canisters → <canister_name>, developers can add a "declarations" config. Options are:
-
"output" → directory to place declarations for that canister | default is
src/declarations/<canister_name> -
"bindings" → [] list of options, ("js", "ts", "did", "mo") | default is "js", "ts", "did"
-
"env_override" → a string that will replace process.env.{canister_name_uppercase}_CANISTER_ID in the "src/dfx/assets/language_bindings/canister.js" template.
js declarations output
-
index.js (generated from "src/dfx/assets/language_bindings/canister.js" template)
-
<canister_name>.did.js- candid js binding output
ts declarations output
<canister_name>.did.d.ts- candid ts binding output
did declarations output
<canister_name>.did- candid did binding output
mo declarations output
<canister_name>.mo- candid mo binding output
Use it with either of these forms:
dfx identity use anonymous
dfx --identity anonymous ...Default identities are the pem files generated by dfx identity new ... which contain Ed25519 private keys.
They are located at ~/.config/dfx/identity/xxx/identity.pem.
Now, you can copy such pem file to another computer and import it there.
dfx identity new alice
cp ~/.config/dfx/identity/xxx/identity.pem alice.pem
# copy the pem file to another computer, then
dfx identity import alice alice.pemBefore, people can manually copy the pem files to the target directory to "import". Such workaround still works.
We suggest to use the import subcommand since it also validate the private key.
Define DFX_WALLET_WASM in the environment to use a different wasm module when creating or upgrading the wallet.
When the caller provides SHA-256 hashes (which dfx does), the asset canister will no longer recompute these hashes when committing the changes. These recomputations were causing canisters to run out of cycles, or to attempt to exceed the maximum cycle limit per update.
The 0.8.0 release includes updates and fixes that are primarily internal to improve existing features and functions rather than user-visible.
This was intended to skip verification of the wallet canister on the IC network, but ended up only writing to the wallets.json file if --force was passed.
-
Support for the latest version of the {IC} specification and replica.
-
Updating to latest versions of Motoko, Candid, and agent-rs
-
Changes to
dfx newproject template and JavaScript codegen to support type inference in IDE's -
Adding webpack dev server to project template
-
Migration path documented at https://sdk.dfinity.org/docs/release-notes/0.8.0-rn.html
Breaking changes to frontend code generation, documented in 0.8.0
dfx deploy and dfx canister install now compare the hash of the already-installed module with the hash of the built canister's wasm output. If they are the same, they leave the canister in place rather than upgrade it. They will still synchronize assets to an asset canister regardless of the result of this comparison.
The streaming callback mechanism now requires the following record structure for the token:
type StreamingCallbackToken = record {
key: text;
content_encoding: text;
index: nat;
sha256: opt blob;
};
Previously, the token could be a record with any set of fields.
Change the default cycle balance of a canister from 10T cycles to 3T cycles.
- Module hash: 1404b28b1c66491689b59e184a9de3c2be0dbdd75d952f29113b516742b7f898
- https://github.com/dfinity/cycles-wallet/commit/e902708853ab621e52cb68342866d36e437a694b
Fixed an issue where the controller can remove itself from the list of controllers even if it's the only one, leaving the wallet uncontrolled. Added defensive checks to the wallet's remove_controller and deauthorize methods.
When using dfx canister sign to generate a update message, a corresponding
request_status message is also signed and append to the json as signed_request_status.
Then after sending the update message, the user can check the request_status using
dfx canister send message.json --status.
Previously, dfx canister call would proxy queries and update calls via the wallet canister by default.
(There was the --no-wallet flag to bypass the proxy and perform the calls as the selected identity.)
However, this behavior had drawbacks, namely each dfx canister call was an inter-canister call
by default and calls would take a while to resolve. This fix makes it so that dfx canister call no longer
proxies via the wallet by default. To proxy calls via the wallet, you can do
dfx canister --wallet=<wallet-id> call.
This change adds the --no-artificial-delay flag to dfx start and dfx replica.
The replica shipped with dfx has always had an artificial consensus delay (introduced to simulate
a delay users might see in a networked environment.) With this new flag, that delay can
be lessened. However, you might see increased CPU utilization by the replica process.
This change introduces the deposit_cycles and uninstall_code management canister
methods as dedicated dfx canister subcommands.
This change updates the dfx commands so that they will accept either a canister name (sourced from your local project) or a valid canister id.
This change allows you to specify the format the return result for dfx canister request-status.
This change fixes a bug where deleting a canister on a network removed all other entries for the canister in the canister_ids.json file.
--network ic now points to the mainnet IC (as Sodium has been deprecated.)
The dedicated candid UI canister is installed on a local network when doing a dfx canister install
or dfx deploy.
This fixes an error which occurred when starting a replica right after stopping it.
dfx now supports a dedicated dfx ledger subcommand. This allows you to interact with the ledger
canister installed on the Internet Computer. Example commands include dfx ledger account-id which
prints the Account Identifier associated with your selected identity, dfx ledger transfer which
allows you to transfer ICP from your ledger account to another, and dfx ledger create-canister which
allows you to create a canister from ICP.
This is a breaking change to support 0.17.0 of the Interface Spec. Compute & memory allocation values
are set when creating a canister. An optional controller can also be specified when creating a canister.
Furthermore, dfx canister set-controller is removed, in favor of dfx canister update-settings which
allows the controller to update the controller, the compute allocation, and the memory allocation of the
canister. The freezing threshold value isn't exposed via dfx cli yet, but it may still be modified by
calling the management canister via dfx canister call aaaaa-aa update-settings
dfx now supports a dedicated dfx wallet subcommand. This allows you to interact with the cycles wallet
associated with your selected identity. For example, dfx wallet balance to get the cycle balance,
dfx wallet list-addresses to display the associated controllers & custodians, and dfx wallet send <destination> <amount>
to send cycles to another wallet.
- Module Hash: a609400f2576d1d6df72ce868b359fd08e1d68e58454ef17db2361d2f1c242a1
- https://github.com/dfinity/cycles-wallet/commit/06bb256ca0738640be51cf84caaced7ea02ca29d
- Module Hash: 3d5b221387875574a9fd75b3165403cf1b301650a602310e9e4229d2f6766dcc
- https://github.com/dfinity/cycles-wallet/commit/c3cbfc501564da89e669a2d9de810d32240baf5f
feat: The wallet_create_canister method now takes a single record argument, which includes canister settings.
DFX will now also delete assets from the container that do not exist in the project. This means if you stored assets in the container, and they are not in the project, dfx deploy or dfx install will delete them.
- now takes arguments as a single record parameter
- must now specify content type and content encoding, and may specify the sha256
Added dfx canister info command to get certified canister information. Currently this information is limited to the controller of the canister and the SHA256 hash of its Wasm module. If there is no Wasm module installed, the hash will be None.
- now takes a parameter, which is an empty record
- now returns an array of records
- use list() instead
feat: add --no-wallet flag and --wallet option to allow Users to bypass Wallet or specify a Wallet to use for calls (#1476)
Added --no-wallet flag to dfx canister and dfx deploy. This allows users to call canister management functionality with their Identity as the Sender (bypassing their Wallet canister.)
Added --wallet option to dfx canister and dfx deploy. This allows users to specify a wallet canister id to use as the Sender for calls.
--wallet and --no-wallet conflict with each other. Omitting both will invoke the selected Identity's wallet canister to perform calls.
Users can use dfx canister sign ... to generated a signed canister call in a json file. Then dfx canister send [message.json] to the network.
Users can sign the message on an air-gapped computer which is secure to host private keys.
-
signandsendcurrently don't proxy through wallet canister. Users should use the subcommands withdfx canister --no-wallet sign .... -
The
signoption--expire-afterwill set theingress_expiryto a future timestamp which is current plus the duration. Then users can send the message during a 5 minutes time window ending in thatingress_expirytimestamp. Sending the message earlier or later than the time window will both result in a replica error.
And add support for http requests in the base storage canister (with a default to /index.html).
This does not support other encodings than identity for now (and doesn't even return any headers). This support will be added to the upgraded asset storage canister built in #1482.
Added a test that uses curl localhost to test that the asset storage AND the webserver properly support the http requests.
This commit also upgrades tokio and reqwest in order to work correctly. There are also some performance issues noted (this is slower than the icx-http-server for some reason), but those are not considered criticals and could be improved later on.
Renamed the project_name in our own generated assets to canister_name, for things that are generated during canister build (and not project generation).
You can now a generate private key via OpenSSL or a simlar tool, import it into dfx, and use it to sign an ingress message.
openssl ecparam -name secp256k1 -genkey -out identity.pem
dfx identity import <name> identity.pem
dfx identity use <name>
dfx canister call ...- Please note that neither the JS agent nor the HTTP server have been updated yet to server such large assets.
- The existing interface is left in place for backwards-compatibility, but deprecated: ** retrieve(): use get() and get_chunk() instead ** store(): use create_batch(), create_chunk(), and commit_batch() instead ** list(): use keys() instead
- feat: dfx now provides
CANISTER_ID_<canister_name>environment variables for all canisters to "npm build" when building the frontend.
- feat: AgentError due to request::Error will now include the reqwest error message in addition to "Could not reach the server"
- feat: Add secp256k1 support (dfx support to follow)
- feat: add option to specify initial cycles for newly created canisters (#1433)
Added option to dfx canister create and dfx deploy commands: --with-cycles <with-cycles>.
This allows the user to specify the initial cycle balance of a canister created by their wallet.
This option is a no-op for the Sodium network.
dfx canister create --with-cycles 8000000000 some_canister
dfx deploy --with-cycles 8000000000Help string:
Specifies the initial cycle balance to deposit into the newly
created canister. The specified amount needs to take the
canister create fee into account. This amount is deducted
from the wallet's cycle balance
- feat: install
dfxby version or tag (#1426)
This feature adds a new dfx command toolchain which have intuitive subcommands.
The toolchain specifiers can be a complete version number, major minor version, or a tag name.
dfx toolchain install 0.6.24 # complete version
dfx toolchain install 0.6 # major minor
dfx toolchain install latest # tag name
dfx toolchain default latest
dfx toolchain list
dfx toolchain uninstall latest- fix: onboarding related fixups (#1420)
Now that the Mercury Alpha application subnetwork is up and we are getting ready to onboard devs, the dfx error message for wallet creation has changed: For example,
dfx canister --network=alpha create hello
Creating canister "hello"...
Creating the canister using the wallet canister...
Creating a wallet canister on the alpha network.
Unable to create a wallet canister on alpha:
The Replica returned an error: code 3, message: "Sender not authorized to use method."
Wallet canisters on alpha may only be created by an administrator.
Please submit your Principal ("dfx identity get-principal") in the intake form to have one created for you.- feat: add deploy wallet subcommand to identity (#1414)
This feature adds the deploy-wallet subcommand to the dfx identity. The User provides the ID of the canister onto which the wallet Wasm is deployed.
dfx identity deploy-wallet --help
dfx-identity-deploy-wallet
Installs the wallet Wasm to the provided canister id
USAGE:
dfx identity deploy-wallet <canister-id>
ARGS:
<canister-id> The ID of the canister where the wallet Wasm will be deployed
FLAGS:
-h, --help Prints help information
-V, --version Prints version information-
feat: dfx call random value when argument is not provided (#1376)
-
fix: canister call can take canister ids for local canisters even if … (#1368)
-
fix: address panic in dfx replica command (#1338)
-
fix: dfx new webpack.config.js does not encourage running 'js' through ts-… (#1341)
-
There have been updates, improvements, and new sample apps added to the examples repository.
All of Motoko sample apps in the examples repository have been updated to work with the latest release of the SDK.
There are new sample apps to illustrate using arrays (Quicksort) and building create/read/update/delete (CRUD) operations for a web application Superheroes.
-
The LinkedUp sample application has been updated to work with the latest release of Motoko and the SDK.