it worked with me finalllly, am using WSL2 on windows 11 ... the script is very restricted in terms where you put the files ...even if you are at the smartpy-cli folder you still need to write the full command as follow:
~/smartpy-cli/SmartPy.sh test ~/smartpy-cli/contracts/play.py ~/smartpy-cli/test
you have to create the "contracts" and "...
I tried this and it is possible. The only thing is, it only partially does what I want. Also, it introduces confusion because we can't do string concatenation for the name, thus it would have to be a generic name.
For what I want to do, which is support a 10,000 NFTs, a better solution would be to have them all in an IPFS file or do a URI based approach. ...
On-chain views are synchronous so you’re mostly good (as good as with regular entry points but even simpler).
However, there are subtle scenarios that can go wrong depending on the assumptions that you make : you should not assume in general that balance is synchronized with state (it’s not) or that no operation is pending.
By storing all tokens' metadata off-chain, the max I was able to push it was to create 425 NFTs in one transaction. In subsequent transactions, the limit is around 250 NFTs per transaction.
def __init__(self, initial_auction_house_address):
# why is the auction house address passed in and not ...
Yes, there is no standard way to do that. However, there is a "URI-pattern" approach, which is non-standard, but I believe it will be, eventually.
The idea is to place the string %token_metadata_uri field in the contract storage, where you specify a URI pattern, telling how to build a link to the token metadata for a token with the given token_id.
From what I see, you have configured an NFT contract, and are trying to use it in the same way as a multi-asset contract (having multiple copies of the same identical token).
Have you considered just using a multi-asset contract? the contract you're using has already implemented the right ledger signature - (owner_address, token_id) -> token_amount. you ...