nathanzebedee / blockchain-research

Hi 👋, I'm Nathan Galindo

A passionate full stack web2 and web3 developer

• 🌱 I’m a fullstack web2 developer with experience in MongoDB, Express, NestJS, React, Node

• 🌞 I'm a fullstack web3 developer with experience in NextJS, TailwindCSS, Rust, Solana tech stack

• 👨‍💻 All of my projects are available at github.com/nathanzebedee

• 📫 How to reach me [email protected]

• 📄 Know about my experiences https://drive.google.com/file/d/1wqdqQjSORIVM-pe_kIFa6GL7PY5XmmGs/view?usp=sharing

• ⚡ Fun fact I am the real slim shady

Connect with me:

Languages and Tools:

blockchain-research's Issues

Implement `update_supplier` function

• update_supplier should allow the updating for supplier information.

updatable information:

• name

• address

• phone

• email

• routing_number

• only passed-in info should be updated (and no other account data)

Implement `create_relationship` instruction

The create_relationship instruction associates two business units together in the form of a Master Edition NFT to create a transactional relationship.

Conditions:

• Relationship consists of 1 Buyer and 1 Seller (business_unit.relationship_function).
• Populate the business_unit.relationships vector with the partner's Pubkey (for each: buyer and seller).

Add error handling for create_supplier function

• Supplier already exists
• Name too long
• Address too long
• Email too long
• Phone too long / too short
• Routing number too long / too short

Implement `destroy_business_unit` method

Create a function that closes a BusinessUnit account.

Rewrite the `update_supplier` function to accommodate new `Supplier` struct

The Supplier struct now includes a relationships attribute which is a Vec<Relationship>. Update the update_supplier function to accommodate the new data structures.

Implement a `create_business_unit` endpoint

The create_business_unit function is responsible for creating a BusinessUnit account on the blockchain.

Associated entities:

• BusinessUnit account
• BusinessUnitArgs for the create_business_unit instruction
• BusinessUnitErrors for create_business_unit error handling

Harden smart contract to re-initialization attacks

Since the CreateSupplier struct uses init_if_needed constraint, we must set up security checks to prevent re-initialization attacks.

Implement encryption for `Supplier` `routing_number` attribute

routing_number is sensitive financial information and requires encryption on the frontend before being submitted to the blockchain.

Add `msg!()` details to each instruction

Replace descriptive comments with msg!() details.

Rewrite test scripts to accommodate new `Supplier` struct

The Supplier struct now includes Vec<Relationship>:

• Test the make_supplier function by passing in an array of objects which match the Relationship struct.
• Test the update_supplier function by passing in an array of objects which match the Relationship struct.

Implement `assign_relationships` endpoint

• Receives a list of relationships
• Validates data for each relationship
• Creates a Relationship account for each relationship
• Links the created Relationship accounts to the Supplier account