existing nft contract?

[maddefientist]

Is there a way to use an existing nft smart contract?

Have tried renaming nft.address in the deploy script, passing the contract address in constructor (wont let me verify with constructor arguments) but it doesnt seem to like anything except the contract deployed alongside the token and staking.

Where would I configure this?

[andreitoma8]

In the deploy script, instead of passing nft.address, pass your contract's address as a string

[maddefientist]

Thanks, I did try that. The stake function refuses to accept the NFT. When I try with an nft id i dont own, it gives proper error "you cant stake what you dont own" , but when attempting to stake properly receive just "fail" - goerli tx hash 0xa98c5ad32f66c259265d14305d988e5229c839a5c37bcbfffe2035cfd27aee57

…

On Thu, Aug 25, 2022 at 10:59 PM Andrei Toma ***@***.***> wrote: In the deploy script, instead of passing nft.address, pass your contract's address as a string — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC674GGGQBQ2O34ZQJYANFDV3BMNBANCNFSM57T66WZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[andreitoma8]

The "you cant stake what you dont own" error is given when you're trying to stake a NFT that is not yours(see require statement at line 61 in the SC). Just to make sure, are you approvin the NFT transfer before trying to stake?

[maddefientist]

Yes, that makes sense if you don’t own the Nft , but the other error shouldn’t appear. The Nft should be approved for transfer, unless I must approve it within this staking contract first ..?

…

On Fri, Aug 26, 2022 at 9:10 AM Andrei Toma ***@***.***> wrote: The "you cant stake what you dont own" error is given when you're trying to stake a NFT that is not yours(see require statement at line 61 in the SC). Just to make sure, are you approvin the NFT transfer before trying to stake? — Reply to this email directly, view it on GitHub <#3 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AC674GBS4RSCWVBMNC4O6IDV3DT5XANCNFSM57T66WZQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[maddefientist]

So I approve each tokenId with the NFT contract for movement, and the staking works. Thank you. Are you aware of any process that makes this flow happen together? Or must all dApps be built to approve specific token ID in your wallet with the NFT collection before staking in Staking contract?

Thanks for your help, if you don't have an answer to simplifying this process please feel free to close the issue

[andreitoma8]

You can use the setApprovalForAll function the first time a user stakes a token so you don’t have to do it with each token every time, as OpenSea does it for example.