-
Notifications
You must be signed in to change notification settings - Fork 102
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reasons for Discontinuance #367
Comments
Yep, blog post here (the site has since been taken down) https://github.com/StrataFoundation/strata/blob/master/packages/docs/blog/2022-11-2-helium-acquisition/index.md |
Thanks, would have been nice if you had returned the tokens before shutting down. |
Returned what tokens? All tokens are either (a) in bonding curves which still function or (b) were returned here https://github.com/StrataFoundation/strata/blob/master/packages/docs/blog/2022-1-19-wumbo-beta-open-dist/index.mdx and here https://github.com/StrataFoundation/strata/blob/master/packages/docs/blog/2022-08-25-sunsetting-wumbo/index.mdx Users of Wumbo had almost a year to exchange social tokens and OPEN for SOL before the blog site was taken down, and the tokens are still in the contracts (now immutable) so they can claim them at any later point. |
Whats bondingcurve? |
That's the address of a fungible entangler. Assuming you hold the wallet https://github.com/StrataFoundation/strata/blob/master/programs/fungible-entangler/src/instructions/close_fungible_parent_entangler_v0.rs Example SDK usage here: https://github.com/StrataFoundation/strata/blob/master/tests/fungible-entangler.ts The contract is immutable and that wallet holds the authority, meaning I can't do this for you. |
After two days in dependency hell and back to old require style i got it working: const anchor = require("@project-serum/anchor");
const { FungibleEntangler } = require("../packages/fungible-entangler/lib/cjs");
const { PublicKey } = require("@solana/web3.js");
anchor.setProvider(anchor.AnchorProvider.local('https://api.mainnet-beta.solana.com'));
var provider = anchor.getProvider();
var program = anchor.workspace.FungibleEntangler;
var fungibleEntanglerProgram = new FungibleEntangler(provider, program);
async function transferAndClose() {
await fungibleEntanglerProgram.transfer({
parentEntangler: new PublicKey('GLq5gk4EKGXm5sKqst8MqW9iJsuM4zGAE65sNv59RWq3'),
amount: 10000000,
});
await fungibleEntanglerProgram.close({
childEntangler: new PublicKey('HK1vum4KFizCSV9ACcdFDxF3tqQbyZNxMW6q2KXwT49V'),
});
await fungibleEntanglerProgram.close({
parentEntangler: new PublicKey('GLq5gk4EKGXm5sKqst8MqW9iJsuM4zGAE65sNv59RWq3'),
});
}
transferAndClose(); The needed addresses i got from the initital transaction: I understand now why there are so many blockchains. Working with this is hell. I guess anyone wants to create something easier to work with (me now too ;-P) |
I seemed to have tried to create a coin with strata some while ago: the setup is very entangled and i do not seem to have the authority over the token. there seems to be a createMetadata happening in the bonding stuff, how was it supposed to be updated? i guess everything was supposed to run through your program? |
The token sale setup was an amalgamation of two different smart contracts -- the bonding curve and the fungible entangler. The issue is that a bonding curve takes tokens into a treasury on one side, then mints new tokens on the other. It has great pricing mechanics, but it has to control the mint authority. That's not always ideal. The way we fixed this was by having the output token of a bonding curve be a kind of shadow token. It's not used for anything but to exchange for the real token in the fungible entangler. It's a bit complicated, yes. But I wouldn't worry about tokens with the same name. People will create spam tokens with the same name of your token, it's unavoidable. The bonding curve has a https://github.com/StrataFoundation/strata/blob/master/packages/marketplace-sdk/src/index.ts#L429 You may find this code useful for disbursing and closing both. |
Whoever created the token should be the authority on the token metadata |
May I ask why it was discontinued?
The text was updated successfully, but these errors were encountered: