nop I used the issue_and_set_all_roles function that the mapper provides

Probably because you have 0 xEGLD to pay for the fees :))

the distant SC has an error but the explorer is not able to recover the error, so there is a problem in your call from sc to sc

You must contact the Elrond team

I am also interested to know how he got those logs pls

since Maiar Exchange is a DEX, anyone can list a token, you don’t *almost* need the permission of anyone (not true at 100% because maiar DEX isn’t yet fully decentralized) Here’s the process to list a token : https://docs.maiar.exchange/token-listing/

swap_remove()

wrapping contract on the mainnet : shard 0 : erd1qqqqqqqqqqqqqpgqvc7gdl0p4s97guh498wgz75k8sav6sjfjlwqh679jy shard 1 : erd1qqqqqqqqqqqqqpgqhe8t5jewej70zupmh44jurgn29psua5l2jps3ntjj3 shard 2 : erd1qqqqqqqqqqqqqpgqmuk0q2saj0mgutxm4teywre6dl8wqf58xamqdrukln

take a look here https://github.com/ElrondNetwork/elrond-lend-rs https://github.com/ElrondNetwork/sc-chainlink-rs

nop

2018

Nop I can use managed types for all sc system proxy functions but not for the transfer ownership, that’s weird lol and i’m in 0.29.3

yeah they removed it just before RIDE on the launchpad, idk why

yes! Here’s my function if you want ? #[only_owner] #[endpoint(changeCollectionOwner)] fn change_collection_owner(&self, new_owner: Address) { let token = self.sft_token_id().get(); self.send() .esdt_system_sc_proxy() .transfer_ownership(&token, &new_owner) .async_call() .call_and_exit() }

you don’t have xEGLD

not an issue about liquidity pool sc’s. If you « want to do » a rugpull like $SQUID, simple : mint a lot of tokens then dump it.

yes i did

you can see here -> https://github.com/ElrondNetwork/sc-dex-rs/pull/165

it is possible since about 3-4 months