Here you can post general questions or issues you have with Solidity smart contracts and Solidity programming.
hi guys i was hoping someone could help. Im in the middle of a project using moralis and when inputting. truffle init, into the terminal the following error appears. C:Users\dell\AppData\Roaming\npm \truffle.ps1 cannot be loaded because running scripts is disabled on this system.
any guidance would be much appreciated pray
Are you trying to run it with powerShell? You should try to use CMD (windows console) instead.
Might be an issue with your powerShell not able to run scripts (maybe admin mode works).
thanks Carlos much appreciated
I’m developer but totally new to blockchain development. I’m about to give Moralis a try for my first blockchain project.
I would like to know if I’ll be able to query Twitter API using some kind of Oracle in a smart contract. For exemple Chainlink have an adapter for Twitter.
It’s still very obscure to me how to setup the whole thing, and I’m not asking “how” to do this (let me the pleasure to discover ). But what I’m asking is : is Moralis a dead end for this kind of requirement? Or will I be able, somehow, to get this working?
I’m a bit concerned about the last part of this article stating that the Node backend has to be configured so the Chainlink adapter can work. Will I be able to integrate this with the Moralis Servers/Functions ?
Does anyone know the process for updating metadata on an ERC721 token? According to the standards it should be possible. https://github.com/ethereum/EIPs/blob/master/EIPS/eip-721.md
In theory, does this mean you could change the image associated with the popular NFT cryptopunks?
Is there a way to guarantee a user cannot change the metadata?
This is the bit I’m referencing from the ERC721 documentation:
A mechanism is provided to associate NFTs with URIs. We expect that many implementations will take advantage of this to provide metadata for each NFT. The image size recommendation is taken from Instagram, they probably know much about image usability. The URI MAY be mutable (i.e. it changes from time to time). We considered an NFT representing ownership of a house, in this case metadata about the house (image, occupants, etc.) can naturally change.
You are referring to ERC721URIStorage. The metadata can be modified by the internal function _setTokenURI. There will need to be another function in your contract that calls _setTokenURI with the correct permissions.
So yes, the way to guarantee a user never changes the URI is to not allow access to _setTokenURI in any functions.
However, it is important to realize why changing an URI may be useful. The biggest use case is in the rare occasion that the file get removed/deleted/banned etc by the host. If _setTokenURI is not available, the NFT would then have to be recreated with a new URI and new transaction history.
More info on ERC721URIStorage here: