Is there a solana/web3 function to return the token id of a NFT?
I'm not sure if that's a thing on Solana or if Opensea is adding those.
For example, opensea says this one is #52
nop, opensea doesn't say this nft is #52. This is taken from name in the metadata and this is not a token id
https://solscan.io/token/31fgM5ZVkDkwwYCWHKXKFWbw2aDXjDpYgj7pjGU46Uhk#metadata
What do you exactly want to do with token Id ?
I think what you are looking for is Token Address
If so, then its in the url. or you can look it on sol scan here:
The closest thing for Solana NFT is the concept of collection https://docs.metaplex.com/programs/token-metadata/certified-collections
Related
Maybe somebody know, im searching for how i can create spl token which will be show in collectible items as nft. I created tokens, I also created an nft collection, and now I’m looking for how to make a token like nft (but not nft). So that after creating the token, by going to the Phantom wallet -> Collectibles, for example, I can see my tokens (not nft). I saw some guys managed to do this, it's interesting how.
Just set the decimals to 0 using "--decimals 0"
How Can I Bind userType with jwt token??
because in the frontend needs to do some operations with type of user(hide some menus if userType is different)
in laravel.. Does it possible?
The way Laravel (and you most likely using https://github.com/tymondesigns/jwt-auth), is that the JWT should probably not carry user types or really other kind of user information than maybe a name or an id. After the token is generated, you are supposed to query another endpoint that will return the user information that you are looking for.
So essentially, what you want is 2 routes, let's say:
POST /auth/login
POST /auth/me
To the first route, you are supposed to provide the username and password, to which you'll get a token if credentials are correct. Then, you take the token you were just given, and call the second endpoint, which will return all user information you might want or need. You don't specify which kind of frontend you are using, but here's an example with Nuxt.js's Auth module: https://auth.nuxtjs.org/providers/laravel-jwt/
I need retrieving all the envelopes that have been signed or sent to an email.
I was trying to do this using the 'accounts/{account_id}/envelopes' endpoint passing the 'search_text' query param. As in the example in documentation https://developers.docusign.com/esign-rest-api/guides/concepts/envelopes/search
/v2.1/accounts/{account_id}/envelopes?search_text=Tabs
But I'm getting always error 400 - INVALID_REQUEST_PARAMETER. Am I doing this in the wrong way?
I think 4644 is most likely not your account ID. can you check what is your account ID?
Also, add :
&from_date=2019-03-04T00:00:00.000Z&to_date=2019-03-07T00:00:00.000Z
On the /payments endpoint, is there a way to know for sure that a payment has been made online and not in a physical store?
I cannot find something about this in this endpoint https://docs.connect.squareup.com/api/connect/v1/#get-payments
The EntryMethod field provides the method with which a form of tender was entered.
https://docs.connect.squareup.com/api/connect/v1/#enum-tenderentrymethod
I know those token spring generates a UUID formatted string. One of my concerns is that it's not really "unique"; it is possible for the UUID to create a token exactly the same as a previous one (of course the odds are VERY small but still possible).
I'm using a database to store my user's token and I'm not sure if Spring checks if the token already exists before creating one in the database?
My second question is : Is it possible to create my own token instead of the UUID format, I'd like to have a more "unique" token like the current timestamp with the user's ID and username and then hash everything and that will be my token instead of 49784c38-43b1-.....
I already have a custom TokenEnhancer that I use to add custom info when returning the token to the client but how can I create a custom token before saving it in my database?
Thanks for you help!
Your TokenEnhancer can use any format it likes for the token value. The custom value will be the one that goes in the ToeknStore (that is the prupose of a TokenEnhancer).
P.S. If you think there might be a clash between UUIDs I think you probably need to do some maths and think again.