# Keep getting this bug when trying to deposit btc to multisig address **URL:** \ **Category:** Counterwallet\ **Created:** [August 7, 2016, 3:25pm UTC](https://forums.counterparty.io/t/keep-getting-this-bug-when-trying-to-deposit-btc-to-multisig-address/2230 "2016-08-07T15:25:01Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![something](https://yyz2.discourse-cdn.com/flex004/user_avatar/forums.counterparty.io/something/32/240_2.png) [@something](https://forums.counterparty.io/u/something)\ **Post date:** [November 1, 2016, 1:59pm UTC](https://forums.counterparty.io/t/keep-getting-this-bug-when-trying-to-deposit-btc-to-multisig-address/2230/6 "2016-11-01T13:59:31Z")
> Is it possible to issue an asset directly from a offline Armory address? I think it is (I assume it’s _your_ address, which you have control of) - basically you need to create a Counterparty transaction first (which you can do in `counterparty-client` on your computer, assuming you haveBitcoin Core addrindex and `counterparty-server`, or Federated Node with counterparty (which includes Bitcoin Core, counterparty-server and counterparty-client)). The nice thing about Federated Node is it runs out of Docker with persistent volumes on the host, so you can install it easily and it’s configured on the fly. Then let it run for 2-3 days until the blockchain and counterparty DB are downloaded ([http://counterparty.io/docs/federated\_node/](http://counterparty.io/docs/federated_node/) has the documentation and instructions). About creating tx outside of CW, take a look at this: > [@How to create a send transaction on Counterparty?](https://forums.counterparty.io/t/how-to-create-a-send-transaction-on-counterparty/2429): > > Let’s assume n4D7ndiC4yLZxhAf726uMHXC914sEuUAcg wants to send n1fseuMLWaKDnDkpXiz8PpwV8RqYna9Mbf one unit of his asset A1517414400000000000. source: n4D7ndiC4yLZxhAf726uMHXC914sEuUAcg destination: n1fseuMLWaKDnDkpXiz8PpwV8RqYna9Mbf asset: A1517414400000000000 quantity: 1 NOTE: This example uses Counterparty and Bitcoin testnet On mainnet the procedure is the same, but for brevity this particle will omit testnet-related notes. In practice: Command line: use testnet=1 in your counterparty se… If you know some JSON, you could use the API, but if you’re more comfortable with the CLI you’d just use the `issuance` action. Example for Testnet: ```auto /usr/local/bin/counterparty-client --config=/home/user/.config/counterparty/client.testnet.conf \ issuance --source YOUR-ARMORY-ADDRESS --quantity QUANTITY --asset ASSET-NAME \ --description "ASSET-DESCRIPTION" ``` It’d spit out the same raw unsigned transaction as in the how-to I linked in this comment, but instead for `send` it’d be for `issuance`. Then you’d sign and broadcast that raw transaction with Armory. If you want to decode the raw transaction to see what’s in it before you broadcast, you can do it out-of-band using another system (e.g. the [public development server](https://forums.counterparty.io/t/how-do-i-get-started-developing-on-counterparty/1198) of CoinDaddy). > [@How to encode and decode a Counterparty transaction](https://forums.counterparty.io/t/how-to-encode-and-decode-a-counterparty-transaction/2426): > > This post explains the process of encoding and decoding Counterparty transactions #Encode You can use one of these methods: Use Counterparty API (e.g. create\_send) to create a raw Bitcoin transaction with embedded Counterparty payload. This approach is easier, but requires access to a Counterparty server or API endpoint. Use any programming language to compose such a transaction manually. This is harder, but does not require a Counterparty server or Counterparty API access. The API (create\_… > To only transfer assets to offline armory is not enough, but to transfer ownership if the issuance is not supported might be another viable option. Does that work? Yes, you can use `--transfer-destination` after the asset has been issued (also use `--unconfirmed` if you haven’t waited for 6 confirmations). ```auto $ counterparty-client issuance --help usage: counterparty-client issuance [-h] --source SOURCE [--transfer-destination TRANSFER_DESTINATION] [--quantity QUANTITY] --asset ASSET [--divisible] --description DESCRIPTION [--fee FEE] optional arguments: -h, --help show this help message and exit --source SOURCE the source address --transfer-destination TRANSFER_DESTINATION for transfer of ownership of asset issuance rights ``` I think you can’t issue 0 quantity, but that’s an interesting question so let’s try: ```auto :~$ /usr/local/bin/counterparty-client --unconfirmed --config=/home/user/.config/counterparty/client.testnet.conf issuance --source n4D7ndiC4yLZxhAf726uMHXC914sEuUAcg --quantity 0 --asset ZEROQTY --description "test for 0 quantity issuance" [2016-11-01 22:11:01][INFO] Running v1.1.2 of counterparty-client. [2016-11-01 22:11:02][INFO] Transaction (unsigned): 0100000001789131f77fa4197014a7d616e543e24d33cb43bb246ec2f78eaabc337cdbf18d010000001976a914f8eb547223b286af4c069845bab650951de0ba8988acffffffff020000000000000000456a43ef337fb72f7e0914e5dd209539337347297a11169a8bbacd8661c5379215dc76e20f0e5eec9e426a75fa97e5cdde8c7e4fc2a9a13cf83fe851682205f7aabe2e27fa37bb423100000000001976a914f8eb547223b286af4c069845bab650951de0ba8988ac00000000 Sign and broadcast? (y/N) y [2016-11-01 22:11:04][INFO] Transaction (signed): 0100000001789131f77fa4197014a7d616e543e24d33cb43bb246ec2f78eaabc337cdbf18d010000006b483045022100f996f54277e1d981d1e8af99dfb536cebf3e138aeff57d77b1fa146f11d329a202202e7bae59bf7f52378d174ccbb012f8db3379328b4a5cd9e192dfaee12acac53301210265f9763ea8f857571a003a9c7abddc9875a3dd921dbdb15c1659944869f945cdffffffff020000000000000000456a43ef337fb72f7e0914e5dd209539337347297a11169a8bbacd8661c5379215dc76e20f0e5eec9e426a75fa97e5cdde8c7e4fc2a9a13cf83fe851682205f7aabe2e27fa37bb423100000000001976a914f8eb547223b286af4c069845bab650951de0ba8988ac00000000 [2016-11-01 22:11:04][INFO] Hash of transaction (broadcasted): 2b3f4a924fe0974781ea6e094b15aec73d2f7b561796de2a50804d4b5a64802d ``` Apparently it works. I haven’t waited so I can’t see it yet, but I suggest you try on testnet first and then check the entire procedure. There’s an explorer here - [https://testnet.counterpartychain.io/issuances](https://testnet.counterpartychain.io/issuances) - but you can also see in your own client using the `balance` or `wallet` command. Note that the testnet is quirky and can take a long time for tx to get confirmed because people are abusing testnet quite a lot. I was going to say if you can’t issue the quantity of zero then you would need to both transfer the ownership of the asset as well as all issued assets, but if it’s possible (it seems it is) you just need to issue the asset and transfer it to another address. Pay attention to divisible/indivisible! Some people discovered that distinction too late (after the launch). If it’s very important to you I’d also suggest to have a backup of the private key or other method stored someplace safe as per usual bitcoin safety best practices. Cool - it just got confirmed - [https://testnet.counterpartychain.io/asset/ZEROQTY](https://testnet.counterpartychain.io/asset/ZEROQTY). --- _[View the full topic](https://forums.counterparty.io/t/keep-getting-this-bug-when-trying-to-deposit-btc-to-multisig-address/2230)._