# Dfx 0.19.0 is promoted! **URL:** \ **Category:** Developers\ **Created:** [April 2, 2024, 4:12pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268 "2024-04-02T16:12:11Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![AdamS](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/adams/32/5248_2.png) [@AdamS](https://forum.dfinity.org/u/AdamS)\ **Post date:** [April 2, 2024, 4:12pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/1 "2024-04-02T16:12:11Z")
## Dfx 0.19.0 is promoted. You can read the release notes [here](https://github.com/dfinity/sdk/releases/tag/0.19.0). This release includes a new `--output json` flag to `dfx canister call`, removing the need to pipe to `idl2json`. JSON format is also used for `dfx ping`. Candid assist mode can now be set to always-on with `--always-assist`, where previously all-optional arguments would be set to `null`. This release also contains the first beta for the cycles ledger; this is still experimental, but you can enable it by setting the environment variable `DFX_CYCLES_LEDGER_SUPPORT_ENABLE`, which will affect any command that would normally use cycles. When fully supported, the cycles ledger enables users to hold cycles instead of using a cycles wallet. Please let us know if you run into any problems. ---
**Author:** ![anon98822045](https://avatars.discourse-cdn.com/v4/letter/a/ce73a5/32.png) [@anon98822045](https://forum.dfinity.org/u/anon98822045)\ **Post date:** [April 2, 2024, 4:58pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/2 "2024-04-02T16:58:33Z")
```auto Apr 02 16:56:53.150 ERRO s:7wqzc-t5wup-ysni3-xmn7x-s7r6l-gvg6t-hjsy2-akfui-oid33-l7jqn-vqe/ n:ckc7s-mn4fb-l5pwv-wv6iu-py7os-sdqoc-uznwl-dtdaa-brgwr-cp56u-aqe/ic_query_stats/state_machine Received duplicate query stats for canister bnz7o-iuaaa-aaaaa-qaaaa-cai from same proposer ckc7s-mn4fb-l5pwv-wv6iu-py7os-sdqoc-uznwl-dtdaa-brgwr-cp56u-aqe. This is a bug, possibly in the payload builder. ``` I think this may be a bug, possibly in the payload builder. ---
**Author:** ![AdamS](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/adams/32/5248_2.png) [@AdamS](https://forum.dfinity.org/u/AdamS)\ **Post date:** [April 2, 2024, 5:00pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/3 "2024-04-02T17:00:09Z")
Was this with `dfx start --clean`, or just with `dfx start`? ---
**Author:** ![anon98822045](https://avatars.discourse-cdn.com/v4/letter/a/ce73a5/32.png) [@anon98822045](https://forum.dfinity.org/u/anon98822045)\ **Post date:** [April 2, 2024, 5:05pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/4 "2024-04-02T17:05:04Z")
I thought I had done --clean, so I just stopped, deleted .dfx and did the whole process again, and it’s not appearing. So yeah, probably wasn’t with --clean EDIT: a minute later… Apr 02 17:06:27.868 ERRO s:jufof-vrfpp-5kmqf-oaqhe-7uco6-pe3ap-mcyay-qz6eg-lfe56-5bwoi-pae/n:wtocv-4tcjc-tkf5a-akqnf-pvnx7-zcaz2-vrwzg-sj7eb-vyumr-qz2vi-4qe/ic\_query\_stats/state\_machine Received duplicate query stats for canister bnz7o-iuaaa-aaaaa-qaaaa-cai from same proposer wtocv-4tcjc-tkf5a-akqnf-pvnx7-zcaz2-vrwzg-sj7eb-vyumr-qz2vi-4qe.This is a bug, possibly in the payload builder. ---
**Author:** ![domwoe](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/domwoe/32/5165_2.png) [@domwoe](https://forum.dfinity.org/u/domwoe)\ **Post date:** [April 2, 2024, 7:31pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/5 "2024-04-02T19:31:47Z")
Has this issue with the Bitcon canister been addressed as well: > [@BTC-integration canister endpoints not returning expected results](https://forum.dfinity.org/t/btc-integration-canister-endpoints-not-returning-expected-results/28395/2): > > Hi @kobby5angels . I can confirm that dfx v0.18.0 will produce the error of IC0501: Canister g4xu7-jiaaa-aaaan-aaaaq-cai is out of cycles. But dfx v0.17.0 worked for me. Prepare Bitcoin Regtest network $ bitcoind -regtest -daemonwait $ bitcoin-cli -regtest createwallet "test" $ ADDRESS="$(bitcoin-cli -regtest getnewaddress)" $ echo $ADDRESS bcrt1qwtcc7xmt9gx99pu0q5976uzdnufccawwc4rfxj $ bitcoin-cli -regtest generatetoaddress 1 "$ADDRESS" [ "3526ba1ec3960eebf0249720f87b11b6e9c2cb1b9856a69276… I assume that this is the reason the Bitcoin canister was downgraded in this release, but might be useful to make this explicit. ---
**Author:** ![lwshang](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lwshang/32/3394_2.png) [@lwshang](https://forum.dfinity.org/u/lwshang)\ **Post date:** [April 2, 2024, 11:21pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/6 "2024-04-02T23:21:30Z")
> I assume that this is the reason the Bitcoin canister was downgraded in this release, but might be useful to make this explicit. That’s correct. We downgraded the bundled bitcoin integration canister in dfx v0.19.0 to address the linked issue. ---
**Author:** ![ilbert](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/ilbert/32/8717_2.png) [@ilbert](https://forum.dfinity.org/u/ilbert)\ **Post date:** [April 3, 2024, 7:56am UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/7 "2024-04-03T07:56:12Z")
Same here: I’m getting this error message every ~5 minutes even if the deployed canister doesn’t receive any method call. I’ve started the replica with `dfx start --clean --host 0.0.0.0:4943`. ---
**Author:** ![Vivienne](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/vivienne/32/29170_2.png) [@Vivienne](https://forum.dfinity.org/u/Vivienne)\ **Post date:** [April 3, 2024, 11:35am UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/8 "2024-04-03T11:35:37Z")
Internal comment on the error message: > Just FYI this bug has no adverse effects, it might just possibly waste some block space. Still not nice to see it… ---
**Author:** ![lastmjs](https://sea1.discourse-cdn.com/flex023/user_avatar/forum.dfinity.org/lastmjs/32/3406_2.png) [@lastmjs](https://forum.dfinity.org/u/lastmjs)\ **Post date:** [April 3, 2024, 1:29pm UTC](https://forum.dfinity.org/t/dfx-0-19-0-is-promoted/29268/9 "2024-04-03T13:29:04Z")
> [@anon98822045](#): > > This is a bug, possibly in the payload builder. I also ran into this error as described here: [Embedding wasm - dfx 0.17.0 crashing where previous version works - #13 by lastmjs](https://forum.dfinity.org/t/embedding-wasm-dfx-0-17-0-crashing-where-previous-version-works/27916/13)