Hello Marcus,
I appreciated your response to my earlier inquiry. I have some follow up questions, regarding the ownership if the API3 Smart Contract and who has access to the funds there? I’m sure that the Smart Contract has a means of allowing the funds to be accessed, or it would be pointless for it to exist. It appears that my tokens were sent to the API3 Contract Address Hash “0xb0f7bfd11bacd0df08c0ba782b3ec9e4f19aa2a7”, and then 0.03173639356105339ETH was transferred to Coinbase. Can you advise why Coinbase would be involved with the contract, and if it is Coinbase or the API3 organization who owns it? If it is Coinbase then perhaps I need to contact them about the return of my API3 tokens. If the contract is owned by API3 and the attached graph shows that they have not been sent anywhere, then whom would I need to discuss this with further? I appreciate your insights on this matter. I have attached a diagram of my research, for visualization I look forward to your response.
The wallet you provided (0xb0f7bfd11bacd0df08c0ba782b3ec9e4f19aa2a7) seems like an ordinary private wallet, with a total of only 7 transactions. There is nothing we can do to restore your tokens in that case. If you can figure out where you got the wallet address from and why you transferred your API3 tokens to it in the first place, you might be able to solve the puzzle and receive your tokens. For instance, if it is one of your alternative wallets that you forgot about, or if you know the wallet owner and could ask him to return your tokens because you sent them by mistake.
As for your previous inquiry that I addressed in April: You have sent your tokens to the API3 DAO governance contract (0x6dd655f10d4b9E242aE186D9050B68F725c76d76). There is nothing we can do about your lost tokens, unfortunately. Tokens that are manually sent to this contract can’t be withdrawn.
If you need assistance with anything else, please let me know.
I initially sent my API tokens to the API3 TOKEN CONTRACT ADDRESS listed on the API3 DAO TRACKER SITE:
Per the diagram I previously forwarded to you. The address 0x0b38210ea11411557c13457d4da7dc6ea731b88a. is the smart contract to initiate the transfer of the API3 token transfer to the entity 0xb0f7bfd11bacd0df08c0ba782b3ec9e4f19aa2a7. Which leads me to ask. If API3 does not own the address 0x0b38210ea11411557c13457d4da7dc6ea731b88a then why is it listed on the API3 website (https://enormous.cloud/dao/api3/tracker). My follow up question, is along the lines of my earlier inquiry. 1) Who set up the Smart Contract 0x0b38210ea11411557c13457d4da7dc6ea731b88a? Because, they set it up to have the API3 tokens withdrawn from my account and transferred to the entity 0xb0f7bfd11bacd0df08c0ba782b3ec9e4f19aa2a7 when the smart contract was activated; and then send 0.03173639356105339ETH - $72.70 to Coinbase. It does not make sense to set up an account (smart contract) to send funds to an account that will never be able to be accessed. If you are unaware of who set up the smart contract. I would appreciate you directing me to someone in the organization that can.
The token contract has nothing to do with the loss of your tokens, you misinterpret the data on Etherscan.
If you look at Etherscan, you can see that you have sent your API3 tokens directly to this wallet. The problem lies on your side. Only you are able to figure out why you sent your tokens to this address, and whom it belongs to. It’s worth to mention that the tokens have been withdrawn from this wallet just minutes after the deposit, so it seems like their arrival was expected.
Prior to this incident, you have sent API3 tokens directly to the API3 DAO governance contract. So it seems that you need to be more careful to avoid incidents like these. Never send tokens directly to any of our contracts. If you want to stake your tokens, please do a deposit by visiting the API3 DAO dashboard.
