BitShares Forum
Main => General Discussion => Topic started by: fluxer555 on February 13, 2015, 08:35:14 pm
-
I noticed this strange transaction just now:
(http://i.imgur.com/uNzk3Ob.png)
In addition to it being strange that I did not initiate this transaction, I have never owned any TOURCOIN, so it is strange that it is possible for me to send any. Here is the transaction details page:
(http://i.imgur.com/C3Ub4cE.png)
And here is a the page from bitsharesblocks, which includes strange data as well:
https://bitsharesblocks.com/blocks/block?id=1772398
What's going on here?
-
Maybe we found a big bug. I escrowed 100 TOURCOIN and released it at the same block. This surely is my transaction.
The txid is #1b7e083a
-
"Bitshares! So anonymous, it covers up who actually send the asset". :P
Looks like a bug with escrow.
-
I think i saw an open escrow in my client lately too .. think owner was clayop .. will check tomorrow
-
This happened to me yesterday. Although different. On Windows 7 I had a Windows message pop up in the bottom right corner out of the task bar where every message pops up when I send or receive a transaction and this time it said one of my accounts, one I never use, sent TourCoin. When looking at transaction records for that account, nothing comes up.
-
FYI, Tourcoin can be used in my friend's tour shop and its value matches 1 KRW. You can pay up to 3% of totalpaent by Tourcoin. LOL
-
FYI, Tourcoin can be used in my friend's tour shop and its value matches 1 KRW. You can pay up to 3% of totalpaent by Tourcoin. LOL
I think you stumbled on a good way to advertise tourcoin. ;)
-
delegate (locked) >>> wallet_escrow_summary
[{
"creating_transaction_id": "4a7efe44c91909c1214762c186b8c57ae12a16f3",
"balance_id": "BTSPYJ6C1CdoyimqmHCcRPEUxJokge1KH9Jg",
"balance": {
"amount": 1000000,
"asset_id": 0
},
"sender_account_name": "BTS111111111111111111113MQ7LD",
"receiver_account_name": "UNKNOWN",
"escrow_agent_account_name": "cyberfund",
"agreement_digest": "0000000000000000000000000000000000000000000000000000000000000000"
},{
"creating_transaction_id": "1b7e083af87d4a78eccb2e91fbacfa4eacb2159f",
"balance_id": "BTSJ2KPSu7tFKW9NPXnWLs3tU6Vr6yPjz1XY",
"balance": {
"amount": 0,
"asset_id": 316
},
"sender_account_name": "BTSHftG7P7TPzTptwoMMyGHHwkGTUYmn1bQM",
"receiver_account_name": "UNKNOWN",
"escrow_agent_account_name": "delegate-clayop",
"agreement_digest": "0000000000000000000000000000000000000000000000000000000000000000"
}
]
Haven't looked into how escrow works yet ..
-
Haven't looked into how escrow works yet ..
By the looks of things, its seriously broken.
-
This is likely a scanning bug related to memo decryption. We used to have the same problem with normal transfers.
https://github.com/BitShares/bitshares/issues/1386