How can I add solana token 2022 metadata?
And how can I add solana token 2022 to phantom wallet?
https://token-creator-lac.vercel.app/
above dapp cant update token2022 metadata.
Related
I wanna create a mint token by phantom wallet, here are the code snippet,
https://github.com/longmengua/contract-solana/blob/9231643fa85ff115404ad37f07453a3d47e160a1/solana/module/components/index/index.tsx#L88
Before minting a mint token, I need to get or create a token account, but somehow the creation of the transaction failed, could anyone help this?
https://github.com/longmengua/contract-solana/blob/9231643fa85ff115404ad37f07453a3d47e160a1/solana/util/getTokenAccount.ts#L5
I have deployed my token to solana network. Because of some change in metaplex metadata so I have to revamp my token. I have to keep token name and symbo, then I did following guide:
https://github.com/solana-labs/token-list#modifying-existing-token
However, these days, seem noone do manual PR to modify token information in solana. I saw some request stay for several weeks already. Does anyone know any other way to update token information in solana?
I am unable to login to my Visual Studio 2019 and I get the warning message We need to refresh the credentials for this account
Based on input from Visual Studio 2017 - How to fix error: We could not refresh the credentials for the account , I have deleted the folder "C:\Users\{username}\AppData\Local\.IdentityService" but it did not resolve the issue
I have checked the logs and I see below message
AcquireTokenException: AADSTS50076: Due to a configuration change made by your administrator, or because you moved to a new location, you must use multi-factor authentication to access
I am using Microsoft Authenticator app to authenticate the request but refresh error keep pops in even though I successfully authenticate myself.
Note: I have ZScalar as firewall. I have even tried switching off ZScalar, but no luck
We're building a Marketplace in NEAR blockchain. Currently, integrating the mint feature.
We have build a NFT contract and deployed to our testnet account. Reference: https://examples.near.org/NFT
We need help with /sign_url API. It generates a link to NEAR Wallet with provided transaction details. May be used to redirect user to the wallet and perform a transaction without generation application-specific keys and granting access:
We have generated approve transaction URL using /sign_url API:
By opening and signing generated approve transaction URL and getting this error:
{"index":0,"kind":{"ExecutionError":"Smart contract panicked: panicked at 'assertion failed: `(left == right)`\n left: `\"mamba11.testnet\"`,\n right: `\"mamba-marketplace-v1.testnet\"`: Unauthorized', /home/gitpod/.cargo/registry/src/github.com-1ecc6299db9ec823/near-contract-standards-3.2.0/src/non_fungible_token/core/core_impl.rs:348:9"}}
Please help us to solve this error.
I had the same issue when i was using mint function inside nft_mint(). The solution was to change mint function to internal_mint according to this example : https://github.com/near/near-sdk-rs/blob/master/examples/non-fungible-token/nft/src/lib.rs#L99 , and without checking owner_id at 98 row! Also you will need to change your near-sdk version to > 4.0.0 and near-contract-standarts to > 4.0.0. And i changed receiver_id type from ValidAccountId to AccountId.
Here are docs with description of internal_mint and mint functions https://github.com/near/near-sdk-rs/blob/master/near-contract-standards/src/non_fungible_token/core/core_impl.rs#L325
I'm currently working on a VSTS Application, but every time I try to Login using my Visual Studio account, it keeps showing the Authorization dialog again. I have to re-authorize my App every time, which keeps generating authorizations on my Visual Studio profile, where the App is registered.
I'm using the OwinOauthProvider for Visual Studio.
https://github.com/TerribleDev/OwinOAuthProviders/tree/master/src/Owin.Security.Providers.VisualStudio
Is there any way to configure to provider to just authorize once and use the authorization for subsequent logins? Or any other suggestions to create a single-sign on from my App and connect to the VSTS Api's?
UPDATE:
Additional links on the issue:
https://github.com/TerribleDev/OwinOAuthProviders/issues/135
https://visualstudio.uservoice.com/forums/330519-team-services/suggestions/9261621-bypass-oauth-grant-step-for-previously-authorized
(vote for it if you're experiencing the same)
There is access token and refresh token, the access token will be expired after an hour, but the refresh token will be expired after one year.
So, you can refresh the access token according to the refresh token instead of let user to authorized again.
Based on this thread (VSTS API Refresh Token Expires), Christopher said that:
We obviously must honor the user's right to revoke a previously
granted authorization
Update:
I analyzed the whole workflow, that is by design, when you request the VSTS external login, the accept page is required, you can’t control it in your code or other ways.