I have changed the contract from the drop down menu whether I deploy wrong contract unfortunately its still not showing. I also increased the gas fees. I have tried severally by using different browser and I also used http and https all to no avail
This is one of the transaction hash of the token I created below:
0xbe8e45ca80fae1de52f60addeae7dbdf0ae75778a3e29f185aa628b7faa0bd7f
The transaction shows up correctly on the testnet BSCScan: https://testnet.bscscan.com/tx/0xbe8e45ca80fae1de52f60addeae7dbdf0ae75778a3e29f185aa628b7faa0bd7f
BSCScan distinguishes between the testnet and the mainnet. So a transaction that exists only on testnet, will not show on the mainnet explorer.
Related
Exactly what I want is this:
I'm transferring money to a contract. The money coming into this contract will be forwarded to the destination address without creating any TXN (that is, anonymously).
I created a contract and the money sent to this contract is sent to the target wallet. In this way, information does not appear in Transaction transactions of the target wallet.
the code i use
receive() external payable {
payable(0x8162Ac860EF729d60C0f3683bfaA0334A3499956).send(msg.value);
}
As pictured (see Transactions)
https://i.stack.imgur.com/OPxH5.png
So far everything is ok. But there is one problem. Transaction appears in Internal TXNs. I want to hide this.
https://i.stack.imgur.com/39nCh.png
What should happen: Money will be transferred to the contract and it will transfer money anonymously without generating any TX belonging to the target wallet.
REQUIRE --->> When the money sent to the contract is sent to the counter wallet, no information will appear in the Transactions and Internal TXNs tab of the counter wallet.
Is it possible to do this? Please tell me what should I do if
possible.
No, this is not possible. Any transfer of a native chain token (BNB in your case of Binance Smart Chain) will appear on an explorer like Etherscan (Bscscan) as an "internal transaction".
I follow this instruction to call smart contracts from DeBot using the message argument in the Surf URI:
https://tonlabs.notion.site/For-developers-f347bd4095f74c9d9e2bd313c666905d
It works ok, but it produces external messages. My guess is that the difference is in headers. How should I modify them to send an internal message using the same scheme?
DeBot cannot send internal message.
DeBot have 3 special features:
calling — get-methods of target smart contracts;
calling — external functions of target smart contracts onchain;
invoking — other DeBot in a local environment.
See DeBot Special Features for more details.
Yes, DeBots themselves cannot do it, so people do the following trick:
Pack debot method arguments into payload:
https://github.com/tonlabs/debots/blob/d8111db9eb5d8c42a362a0d34a4dea38f6789eec/accman/AccMan.sol#L257
Run sendTransction with the address of the current DeBot (to) and the address of a wallet (from). The wallet aka smart contract must obviously have sendTransction.
The external message is received by the wallet, and the multisig sends an internal message to the method in payload.
Once the DeBot receives this internal message, it can tunnel them to other smart contracts.
The step can be simplified, so that sendTransction is sent directly to the smart contract which requires internal message by providing the correct payload parameters (method name and params).
I think previous answers are indeed "best practice", but still incorrect. Of course, you CAN make internal messages without any additional Msig. DeBot is a smart-contract too. You just have to do the call like this:
address myDebotAddr = address(this);
IMyDebot(myDebotAddr).myFunction{...}( ... );
DeBot will call his own contract that lies in blockchain. Then in the function myFunction() you should:
have tvm.accept();
do the internal call that you need
Thus the execution of myFunction() will happen in blockchain, not locally.
Still, you will have to add funds to debot balance. So, it's not a "best practice" for widely used DeBots.
i have the code in solidity, i'm wondering something: I deploy code for the 0x583... first, i send 1 eth to another account. Before i click withdrawAllMoney, i click destroySmartContract, 1 eth 's automatically send to receiver (this is okie!). But after that, i keep going send the 1 eth from 0x583.. to another account, it still take out eth from 0x583.. but the orther can't receive it.
I'm wondering: when i call the selfdistruct, is the contract real deleted (can't send or recieved...)
Thank you!
when i call the selfdistruct, is the contract real deleted (can't send or recieved...)
selfdestruct() effectively removes the deployed bytecode from the contract address.
In the next block, this (former contract) address will act as a regular address without a smart contract, so it is able to receive tokens and ETH.
But, since it doesn't hold any bytecode anymore, you won't be able to interact with the contract (it's not there anymore).
I am playing around with the lightning implementation from https://github.com/ElementsProject/lightning and after the following steps the cli-client cannot list funds which I deposited at the generated address from the internal wallet
I installed bitcoind-0.16 and fully synced the mainnet-blockchain
I installed c-lightning and synced with the local full node
I generated a new address with ./lightning-cli newaddr
I funded this address from my Electrum wallet (not from the local node wallet) and saw the incoming transaction with ./lightning-cli listfunds
Then I accidentally deleted the file .lightning/lightningd.sqlite3
After restart the lightningd recreated the file but now ./lightning-cli listfunds is showing empty results but the funds have to be there because the funding transaction is visible in the blockchain.
I investigated ./lightning-cli dev-listaddrs which shows all addresses of the internal wallet and there is my funding address. So I think I need to re-sync the lightningd with the bitcoin blockchain, but a ./lightning-cli dev-rescan-outputs had no success.
What can I do to be able to see and spend the funds again? Or, how can I get the seed/private key of the internal (lightning) wallet?
A perfect answer was given from a c-lightning member here: https://github.com/ElementsProject/lightning/issues/1170
In case the link dies:
Well, the short answer is do not delete the db, that will end up losing funds, just like deleting the wallet.dat would in bitcoind.
The long answer is, use newaddr to regenerate all addresses you had (it's ok to call it a few times too many). Then stop lightningd, open lightningd.sqlite3 and tell it to scan from an earlier block:
sqlite3 $HOME/.lightning/lightningd.sqlite3 "UPDATE vars SET val= 500000 WHERE name='last_processed_block';"
Then restart lightningd and it should start scanning the blocks from height 500'000 (which will take quite some time).
Notice that this only works as long as you don't have channels open, since in that case you're no longer the sole owner of the funds. So never delete the DB!
I'm looking at this: https://mtgox.com/api/2/stream/list_public?pretty And I only see one: "trade.BTC": "dbf1dee9-4f2e-4a08-8cb7-748919a71b21"
When trying to connect to it, I'm getting very odd trade data, which, when compared to what I see on BitcoinWisdom doesn't really correlate. Where do I find an actual channel for BTC/USD trade and also what are the addresses for other currencies trades?
Its d5f06780-30a8-4a48-a2f8-7ed181b4a13f
Try the following in the PubNub dev console to see the messages on this channel
https://www.pubnub.com/console?sub=sub-c-50d56e1e-2fd9-11e3-a041-02ee2ddab7fe&pub=demo&channel=d5f06780-30a8-4a48-a2f8-7ed181b4a13f&origin=pubsub.pubnub.com&ssl=true
You can also check http://rtbitcoin.co/ (PubNub Bitcoin Exchange solution kit) for more info
Also check a related stackoverflow post here