Describe the bug
The name field of the fanout account is saved as is from the input of the user. It does not follow the pattern of puffing out the string to the max length allocated for the field within the account.

Example from Metaplex Program Library
https://github.com/metaplex-foundation/metaplex-program-library/blob/f39cbb663ba499c4167ad6e0cf6509b9367cf271/fixed-price-sale/program/src/utils.rs

Code saving the name within Hydra
https://github.com/GlassEaters/hydra/blob/main/programs/hydra/src/processors/init/init_parent.rs#L52

To Reproduce
Create a fanout with a name less than 50 characters.

Allow optional Configuration to allow a reward for distributors. They should get their txn fee + some non-trivial amount of money to continue to distribute.

1. new/existing fanout, with token style
2. I, fanout authority, want to use some of my tokens to stake on someone else's behalf:
   a. I create a tokenacc if needed
   b. send em tokens? in same instruction set
   c. stake them for them?

alternatively could I delegate them some? or some shit lol

--> this doesn't work

usecase: airdrop

I trying to see if I can use Hydra to act as creator wallet for NFTs.

I created a Fanout, added the shares, and got the Fanout address and Native account address.

When I send SOL to the Fanout address, then the distribute shows no balance, as the SOL needs to go to the Native account. So, if I was to use Hydra for royalties coming from regular Marketplaces (such as Magic Eden), then I'd have to use the Native account.

When I tried to send SPL to the fanout address, the balance shows and can be distributed properly.

The thing, I'm also creating a custom marketplace (with LIQNFT) that will work with a SPL, so it'll distribute SPL royalties to creators in the NFT.

So the problem I'm facing is not being able to use a single address to put as creator of the NFTs so whether SOL or SPL arrives there, then Hydra will be able to distribute.

Any suggestions I could do?

I looked at the program code, but couldn't find a way to move the funds from the Fanout address to the Native account, that would work as a escape hatch.

Describe the bug
When trying to create a wallet in mainnet-beta the transaction is always sent to devnet

To Reproduce
Steps to reproduce the behavior:

1. Go to https://hydra.glasseaters.xyz/?cluster=mainnet-beta
2. connect wallet
3. Make sure that mainnet cluster is chosen
4. Create a fanout wallet

Expected behavior
Wallet should be created in mainnet-beta. Not devnet

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Windows
• Browser chrome
• Version 101

hi all, i used hydra sol wallet address as creator in the candy machine V2.
I would like to sign the metadata as verified creator, but there is no keypair from fanout wallet available,,,

p.s. I used https://hydra.cardinal.so/ to create the fanout wallet which give me the FANOUT ADDRESS and SOL WALLET ADDRESS.

anyone have idea on how to deal with? much appreciated

Hi,

would be nice for an optional argument setting a future date (be rent epoch?) by which the tokens will be eligible to unstake :)

Hi technical geeks, I need help in calling hydra SDK. I am able to sucessfully send airdrop of SOL but when I try using sending SPl20 token with the below given reference code I get error:
{InstructionError: Array(2)}InstructionError: Array(2)0: 11: {Custom: 6012}length: 2[[Prototype]]: Array(0)[[Prototype]]: Object

in the following code, I am able to pay claim2 but not claim

async function claim(){
if (wallet){ let fanoutSdk: FanoutClient;
fanoutSdk = new FanoutClient(
connection2,
// @ts-ignore
wallet
);
const fanout = new PublicKey("2DdevS3SFCsuUBAjnhi4krz1GSvDenZfMETaHqWFWUn9")

let ix = await fanoutSdk.distributeTokenMemberInstructions(
{
fanoutMint: new PublicKey("DLbjx3D65yP7yy4eKSfMFzUgvTfKB9ApTXYunA2NUMtF"),
distributeForMint: true,
membershipMint: mintPublicKey,
fanout: fanout,
member: wallet.publicKey,
payer: wallet.publicKey

}

);
let tx2 = await fanoutSdk.sendInstructions(
ix.instructions,
[],
wallet.publicKey
);
}
}
async function claim2(){
if (wallet){ let fanoutSdk: FanoutClient;
fanoutSdk = new FanoutClient(
connection2,
// @ts-ignore
wallet
);
const fanout = new PublicKey("2DdevS3SFCsuUBAjnhi4krz1GSvDenZfMETaHqWFWUn9")
let ix = await fanoutSdk.distributeTokenMemberInstructions(
{
fanoutMint: new PublicKey("BAjRRdbhNWwc1SWWHNHGLGtqS1kDct78qz9oGqGcL6H9"),
distributeForMint: true,
membershipMint: mintPublicKey,
fanout: fanout,
member: wallet.publicKey,
payer: wallet.publicKey

}

);
let tx2 = await fanoutSdk.sendInstructions(
ix.instructions,
[],
wallet.publicKey
);
}
}

mmmm

money goes in circles

mmmmmmm

leaving this for later

Describe the bug
https://hydra-dox.vercel.app/ -> Now leads to a 404 not found.

To Reproduce
Just visit the documentation link above.

Expected behavior
The docs for hydra should appear

Screenshots

Hydra currently does not support adding wSOL as an SPL token when calling initializeForFanoutMint. The function violates a raw constraint on the method.

Upon further research, the constraint in question can be found here:
constraint = mint_holding_account.is_native() == false,

The issue is that wSOL is an SPL token, but also considered a native token. The associated token account created violated this constraint. Is there a way we can modify or remove this constraint to support wSOL?

Description

The SDK package uses some packages not listed in its dependencies, which yarn complains about. For example:

Error: @glasseaters/hydra-sdk tried to access @project-serum/anchor, but it isn't declared in its dependencies; this makes the require call ambiguous and unsound.

To Reproduce

Given the following file (index.ts):

import { Connection, Keypair } from '@solana/web3.js';
import { FanoutClient, MembershipModel } from '@glasseaters/hydra-sdk';
import { NodeWallet } from '@metaplex/js';

(async () => {
  const connection = new Connection("devnet", "confirmed");
  let fanoutSdk: FanoutClient;

  const authorityWallet = Keypair.generate();

  fanoutSdk = new FanoutClient(
    connection,
    new NodeWallet(authorityWallet)
  );

  const init = await fanoutSdk.initializeFanout({
    totalShares: 100,
    name: `Test${Date.now()}`,
    membershipModel: MembershipModel.Wallet,
  });
})();

Run the following commands:

$ yarn init -y
$ yarn add --dev typescript @types/node ts-node
$ yarn add @solana/web3.js @metaplex/js @glasseaters/hydra-sdk
$ yarn exec ts-node index.ts

Expected Behavior

Dependencies should be included in the SDK's package.json

Describe the bug
In both the GUI and the SDK, the ProcessDistributeNft program call always results in an IncorrectOwner error. In this CLI I've attempted to use distributeAll, distributeAllInstructions, and distributeNftMemberInstructions and each call results in an IncorrectOwner AnchorError.

To Reproduce

1. Use the NFT membership model in the GUI
2. Fund the Hydra account with tokens
3. Hit the Hydra button and watch the JS console.

Expected behavior
The hydra button or the distributeAll command in the SDK should distribute tokens.

I may do this for my own sake just putting this here so we all remember

my user error has cost me these 1.5 sols:

https://solscan.io/account/7SWQ8CK8BMvZFpVJ7a1vfVC14Cdw4Jsc7CZpkmRtnQCY