Hi,
About “the first one does not record changes as the transactions go through” do you mean the buying transactions in the log? please recall that only buying transactions are registered. And about the graphics section, the graphics shows after two buying transactions are made.
About the token issue can you share the address of the Suika contract that is giving errors?
Thread Starter
pejeto
(@pejeto)
Hi,
This contract gives an error: 0xe94D535B6d19666BaD9B39B1B253EdcdAe97Ea4C
Here is a link to a page: https://tradplay.com/nft-collection/tradstampzero/
On this contract we would like to change the payment token: 0x85AC046ca55095C45cF9bDba380a3E5A1e5eDDF1
No changes have been saved since the update, but payment for the change has been made.
Here is a link to a page: https://tradplay.com/nft-collection/tso/
Thank you for your cooperation.
-
This reply was modified 4 years, 3 months ago by
pejeto.
Ok, here it is what I see:
This is a valid Suika smart contract:
0x85AC046ca55095C45cF9bDba380a3E5A1e5eDDF1
That have this as a payment token:
0xB8c77482e45F1F44dE1745F52C74426C631bDD52
But this page:
https://tradplay.com/nft-collection/tradstampzero/
is set to work with this contract:
0xe94D535B6d19666BaD9B39B1B253EdcdAe97Ea4C
Which is not a valid Suika Smart Contract
So, what you need to do is follow the instructions here:
https://wpsmartcontracts.com/docs/doc-load.php
To manually load this Suika Smart Contract:
0x85AC046ca55095C45cF9bDba380a3E5A1e5eDDF1
Thread Starter
pejeto
(@pejeto)
Oh, you are right 0xe94D535B6d19666BaD9B39B1B253EdcdAe97Ea4C is a valid Suika contract. Sorry about that.
And about the change in the payment token, you should be able to do it connecting your metamask account using the same account you used to create the smart contract and then go to NFT Collections, edit the collection and change the “payment token” field and click update
Thread Starter
pejeto
(@pejeto)
Do you have an answer to my question why a valid contract -> 0xe94D535B6d19666BaD9B39B1B253EdcdAe97Ea4C
with a valid token -> 0xB8c77482e45F1F44dE1745F52C74426C631bDD52
gives an error?
Why change the contract three times in the way you describe.
I pay for these changes:
https://www.oklink.com/en/oec/tx/0xa9da6ef9c39f298b78c5837e78daaa765556e2f6253e46e32223dddd5b47f450
https://www.oklink.com/en/oec/tx/0x8d6925a78cdbaa2da6dd8ec3a66b18befab92aa3cae54cd5dd566cef5c2a989b
https://www.oklink.com/en/oec/tx/0x5aa158e539130590af37c4a0a7bb523e82bc9a3bb64177f176c5df609f60fe47
and the problem continues.
I ask for more serious support.
Thread Starter
pejeto
(@pejeto)
Hello,
do I understand that there is no solution to the problem?
Also, how can I trust the security of the money that will pass?
thanks
We are seeing this error:
Returned values aren’t valid, did it run Out of Gas? You might also see this error if you are not using the correct ABI for the contract you are retrieving data from, requesting data from a block number that does not exist, or querying a node which is not fully synced.
That may be an error with the OEC RPC endpoint, unfortunately we haven’t found an alternative RPC for OEC.
And about the money all tx are handled by metamask, we never touch the keys, and the code contracts is open and verified, so feel free to run an audit or a code review by some expert on the field.
