Sending a token to some people without waiting confirmation.
What I did:
1 Create new wallet on wallet.counterwallet.io
2 Send BTC and LTBCOIN to the new wallet
3 Wait for the confirmation
4 Send LTBCOIN to 5 addresses.
5 Check the transactions on Blockscan.com. But only one unconfirmed transaction is showed.
My expectation is five unconfirmed transactions. As far as I can see Google developer console, “create_send” api has allow_unconfirmed_inputs=true option. This option seems to be disable.
Although "Tokenly Pockets” does not use countepartyd server, I can see all of transactions when I tried same thing from the Chrome Extension. That is what I want to do.
Why I asked this question:
I have my own counterpartyd and the same issue is happened. I want to solve it.
Signed txes were created and broadcast is also completed. Thare are two strange things. One is the lenght of (1)'s signed tx is different from others. The second is http://blockscan.com/txInfo/11790934 shows TX_hash is d196ca671afc85ba6d4e74e01e03a99ecac3a9bef99bc4564b69a68239cb6423. The value does not include the return value of “broadcast_tx” API.
Signed tx and tx_hash from Google developer console.
(1)
signed tx:01000000028a37e943eaea7f4ec47418f1b2fc252948126ae72aa239a21e6b26ff486e501d000000006a47304402205168fe392982ec6a58dfe92a9f21ef3b607e49bc1104e3c1df06be1af8cfbffc02202466fcd6788185f8ea928899e45aebf949395951f3f7a433943b9a3d099ef01501210357edf471a1060a1279c2863238051aaa6379290b365cc7e2045336d2ba938538ffffffffab74a5b00116fa05581832e2dfec66886325b008a3ff4539ffe14e76c7432389010000006b48304502202a86b84e41f1107ca547956e63a9c3529e4eab14ac69a9b7e1022ee136286bf9022100cf755828acf2596db6cf2a294854e7804f19908243bbbc8b640044d78c9e127601210357edf471a1060a1279c2863238051aaa6379290b365cc7e2045336d2ba938538ffffffff0336150000000000001976a9144344e1d44aac38bd591e31d52856548d591fdd9a88ac00000000000000001e6a1c94d60c873066f6a2c32b50e65878279f6f91bd9ccf4c0d3f404060ef905f0100000000001976a9140760ccc1c3cf5bbeea71f67cc188173a3561381488ac00000000
(2)
signed tx:010000000125cf53179253e6b09c4fed7d50ec009683130f095f9b0d49331be73ed3784901020000006b483045022100eadb705f7ca44bb3301b3d4b9d09789f292f980736dbd611d239a0072fb5389702202ec5a95e0ddd1674b61b0cbebb59f84a49767fc7a24b509bebdbd54ddce208de01210357edf471a1060a1279c2863238051aaa6379290b365cc7e2045336d2ba938538ffffffff0336150000000000001976a9144344e1d44aac38bd591e31d52856548d591fdd9a88ac00000000000000001e6a1cb8bca0a03807a7695ea6e792058a962805b3c53199b9d3043062f9254a230100000000001976a9140760ccc1c3cf5bbeea71f67cc188173a3561381488ac00000000
(3)
signed tx:01000000017de1b335562f77dccb646b24ed1e9690f2ea5985351fda8cc9fdabdbdc2eddb9020000006c4930460221008514ee3584c627aa350f17436ab29fe42d08f90b9c634a8ae9435cd8e2736e1e022100f3005575bf366a2baac14babe4c383d8da089fe965c6006f54584a44042ababd01210357edf471a1060a1279c2863238051aaa6379290b365cc7e2045336d2ba938538ffffffff0336150000000000001976a9144344e1d44aac38bd591e31d52856548d591fdd9a88ac00000000000000001e6a1ca2f52f9316b9caf9d065977c17136bf91223b221da88a10d2b3e622904e70000000000001976a9140760ccc1c3cf5bbeea71f67cc188173a3561381488ac00000000
(4)
signed tx:010000000130075373aab215f6d902653294e9cb213cd9daed9c236b9239185a487b5398a2020000006b483045022100811c5fa1d7acace2fa4f59fada96e6b97c9ed87881eb40bf278344e5ffd0f61102206dd8f3be52e16d9437e938592d1bb724f72df63e845c98881fea1c012e0478d201210357edf471a1060a1279c2863238051aaa6379290b365cc7e2045336d2ba938538ffffffff0336150000000000001976a9144344e1d44aac38bd591e31d52856548d591fdd9a88ac00000000000000001e6a1cbd1cf972c911fa07f0494f54fe4ee302e957b09d8d10a5fae6ee8f29beaa0000000000001976a9140760ccc1c3cf5bbeea71f67cc188173a3561381488ac00000000
(5)
signed tx:01000000012a523a0c9d31f0402c1c68a16c68f79e6ce7a1a29298344b96a47dbdae27dffc020000006b4830450221008e7ef31a156a990ee630880daa26ac572002d11388aba66ebf93eefde83797a102200b903d7f340f2d64d2de85a4b1326cc1c88a643a40725c8a25e4d20c4fca015d01210357edf471a1060a1279c2863238051aaa6379290b365cc7e2045336d2ba938538ffffffff0336150000000000001976a9144344e1d44aac38bd591e31d52856548d591fdd9a88ac00000000000000001e6a1c14bcb902f70ab160d02d9079d39f8629725debc38424b57fe0296fba786e0000000000001976a9140760ccc1c3cf5bbeea71f67cc188173a3561381488ac00000000
Thank you for reply. I think counterwallet.io is using “allow_unconfirmed_inputs=true” option. But I could not send tokens until the confirmation. I used “https://wallet.counterwallet.io/”. So I thought that “allow_unconfirmed_inputs=true” did not work properly. (I did not get any errors. Sent notification was showed on the page but the transaction did not show blockscan and blockchain.info even I waited for a long time)
My question is … is it possible this case below?
(1) Send a token to an address on counterwallet.io.
(2) After (1), (1) is still unconfirmed, send a token from the same sender address to another address on counterwallet.io.