TON Dev Chat
get_data()
is not a get method, but alias for c4 PUSH
(push contract storage on stack) declared in stdlib.fc. You can make get method wrapper for get_data()
, but usually methods for retrieving data about account, for instance getAddressInformation already contain contract storage field.load_msg_address
does a little bit more than just reads 267 bits: it reads MsgAddress structure which in most cases indeed is presented by 267 bits (2 bit tag, 1 bit anycast, 8 bit workchain, 256 bit address part), but sometimes may be presented by other constructors like addr_none (2 zero bits), addr_var, addr_extern etc, see here. So load_msg_address
automatically detects what the address type it sees and read exactly that.
transfer
method.
receive external
.
import nacl from 'tweetnacl';
const keyPair = nacl.sign.keyPair.fromSeed(
Uint8Array.from('12345678912345678912345678912345')
);
ton-crypto
const key = await keyPairFromSeed (await getSecureRandomBytes() )
ton
lib not tonweb
so I thought I'd go with ton-crypto
ton
had packed something like nacl
as utils
jtton-wallet.boc
exists?
e
letter
libcrypto.dylib
file to replace the old one, but I'm encountering another issue now
-SPA
flags: they will add needed libs and wrappers
lite-client -C testnet-ton.json -c "sendfile wallet-test-receiver0-query.boc"I get
0.004760001
TON
for this contract. That is $0.003
currently.
b'\xb5\xee\x9crA\x01\x01\x01\x00$\x00\x00C\x80\x1e 4a,\xab\xfd\xa6\xd9\xb9b^A\x88\xa4\xe34\xbd\xfb\xb2\xfe\x95\xc7\xadOt\xed\x88\xdfO\xf1\xa6P\xcb\x7f\xfe`'
EQBoDpISRfTxy320u0l1vX0fFVaQYTQDMD0EA7SpgF3aVbaX
numberEQBoDpISRfTxy320u0l1vX0fFVaQYTQDMD0EA7SpgF3aVbaX
const minter = new JettonMinter(tonweb.provider, {what is jetton content uri ?
adminAddress: walletAddress,
jettonContentUri: 'https://ton.org/jetton.json',
jettonWalletCodeHex: JettonWallet.codeHex
});
panic: invalid boc magic header
site:
in bots api and ton docs websites, but no result. The only official mention of this feature I could find is this tweet by ton_blockchain.await fromWalletA.deploy().send(toNano('0.05'));
) has commission -> -0.05fift -s wallet.fif
(or analogous), whether the source smc has sufficient founds or not, what i get as response from the liteclient or tonlibjson is:[ 3][t 2][2022-07-02 13:09:03.344361685][lite-client.cpp:1160][!testnode] external message status is 1But in one case we get the funds transferred, in the other we end just with and external message which consumed some grams in the source smc.
get_nft_content
section.
gen-zerostate.fif
I even like this idea. Perhaps in the future we will experiment with this :)