Introducing B3Pay - Your Trusted Partner for Protocol Canister Management

[b3hr4d]

Dear ICP Community,

As we approach the exciting phase of voting for grants next week, we at B3Pay are thrilled to present our candidacy for the Protocol Canister Management grant ($5000/month). We believe our team’s unique blend of expertise, passion, and commitment to the Internet Computer (ICP) ecosystem makes us an ideal choice for this crucial role.

Who We Are: The B3Pay Team

B3Pay boasts a team of dedicated developers committed to pushing the boundaries of what’s possible on the Internet Computer. Our mission is to create a robust, cross-chain payment system that seamlessly integrates Bitcoin, Ethereum, and the Internet Computer.

Meet our core team:

1. Behrad (Manager and Founder)

   • 12 years of web development
   • 4 years of Ethereum development
   • 2 years of intensive ICP development
   • Strategic visionary and project management
   • GitHub | X

2. Ali (AI and Machine Learning Developer)

   • Expert in Machine Learning and Deep Learning
   • Specializes in integrating AI solutions into ICP projects
   • GitHub

3. Bahamin (Motoko developer)

   • Specializes in Motoko, the native language of ICP
   • Focused on building robust decentralized applications
   • GitHub

Our Achievements: Shaping the ICP Landscape

We’re not just talkers; we’re doers. Here’s a snapshot of our contributions to the ICP ecosystem:

1. B3Forge: Revolutionizing canister interactions with an enhanced Candid UI.
2. B3Wallet: A next-gen wallet for ICP assets, featuring multi-signature and multi-chain support.
3. B3Note: Bringing secure, decentralized note-taking to ICP with end-to-end encryption.
4. ic-reactor: Empowering developers with a cutting-edge frontend library for ICP DApps.
5. B3Utils: Simplifying ICP development with our comprehensive Rust library.
6. ETH Payment Tutorial: Bridging worlds with our guide on Ethereum-ICP payment integration.

Our Commitment as a Voting Neuron

We’re not just applying for a grant; we’re committing to a pivotal role in shaping the future of ICP. Here’s why our participation matters:

1. Active Development Team: We are a full-time development team, deeply involved in the ICP ecosystem. Our participation as a voting neuron allows us to influence the ecosystem’s direction, ensuring that it remains secure, decentralized, and developer-friendly.
2. Expertise in Canister Management: Our team has a deep understanding of canister management, which is essential for the security and efficiency of the ICP. As a known neuron, we can contribute to maintaining and improving these protocols.
3. Promoting Decentralization: We are committed to decentralizing the governance process. By being a known neuron, we can help distribute decision-making power more evenly across the community.
4. Strategic Project Involvement: Proposals like 131701 “Upgrade the ICP Ledger to fully support the ICRC-21 standard” are directly relevant to our work. Implementing this standard is crucial for our future projects, making our involvement in the voting process a win-win for both our team and the entire ICP ecosystem.

Why Choose B3Pay?

Selecting B3Pay as a known neuron for canister management means choosing:

• A team with a proven track record of innovative ICP projects
• Developers who understand the technical nuances of protocol management
• Advocates for a secure, efficient, and developer-friendly ICP ecosystem
• A group committed to transparent and community-oriented decision-making

Join Us in Shaping ICP’s Future

We are planning to submit a known neuron proposal in the next week or so to offer others a known neuron to follow us on canister management proposals.

• Neuron ID: 16122208542864232355

Best regards,
The B3Pay Team

---

Have questions or want to learn more? Reach out to us on the forum.

[alifrmf]

Proof of work as a voting neuron:

As a member of the B3Pay team, in this post, I’ll indicate the steps I’ve taken to verify an NNS Canister Upgrade Proposal, specifically focusing on ensuring that the Wasm code aligns with the specified source code repository. Below is the detailed process I followed to verify the Wasm hash, upgrade argument, and the governance canister ID for the proposal to upgrade the Ledger Canister.

I located the specific NNS Canister Upgrade Proposal I intended to verify 131701.
I cloned the ic repository, which includes the proposed changes for the canister upgrade. After cloning, I fetched the latest changes to ensure I had the most up-to-date code.

To ensure I was examining the exact version of the code linked to the proposal, and checked out the specified commit using the following command:

git checkout 2bdfdc54ccc7ef27dd7b4f37aaea172198dce6ab

After checking out the correct commit, I built the Wasm file to verify its hash. Then I compared this hash with the one provided in the proposal, confirming that the proposal’s claim was accurate and that the Wasm code was as expected.

[Bahamin1]

As a Member of the B3Pay Team, Here’s How I Approved Proposal #131701 Similar @Ali did :

Proposal Summary:

• Proposal to Upgrade the Ledger Canister
• Proposer: DFINITY Foundation
• Git Hash: 2bdfdc54ccc7ef27dd7b4f37aaea172198dce6ab
• New Wasm Hash: 5714a608b4c0af565c5c348e7c54e837512bc47e8f271add6bcd680ec72ef9a0
• Upgrade Args Hash: 10bc8d3f78b366304e4a41383fa486584474f82ab1641b23078d5cb9a0806819
• Target Canister: ryjl3-tyaaa-aaaaa-aaaba-cai

To begin, I will perform the initial verification steps similar to what @Ali did:

Check Git Hash, New Wasm Hash, and Args Hash (as demonstrated in the attached screenshots).

After that :

Analyze and Check Changes: I will thoroughly analyze and check the changes, noting any modifications in the code (as illustrated in the provided example).

Document the Analysis Process: I will continue the analysis process until completion, ensuring detailed documentation of all changes.

Review and Confirmation: I will review the changes and confirm their accuracy against the proposal details.

Finally, I will forward my observations and conclusions to @b3hr4d, our Team Leader, for a final review and decision.

[alifrmf]

Next, for the argument verification, I used didc command to create the verification file from arguments, it was confirmed that the proposed args hash is the same as the generated hash we obtained.

Finally, I verified the governance canister ID to ensure that the proposal was targeting the correct canister.

[b3hr4d]

If you believe in our vision and would like to see us as one of the voting neurons, we’d appreciate your support! Please consider voting for our proposal: Voting grant application of B3Pay for topic Protocol Canister Management.
Your vote can make a difference in shaping the future of the Internet Computer.

[b3hr4d]

Hi ICP Community,

Thank you for your support! We at B3Pay are excited about the upcoming voting phase and our proposal to become a Known Neuron.

We would greatly appreciate it if you could vote for our proposal:

Register Known Neuron: B3Pay

[tiago89]

Hi Behrad,

Just to let you know that the proposal that was submitted was under “motion” type, but it should have been by “Register Known Neuron”.

Can you submit a new one?

Thanks

[b3hr4d]

Hi @tiago89,

Thanks for catching that! I appreciate your help. I’ll submit a new proposal with the correct type, “Register Known Neuron” soon. I’ll keep everyone updated once it’s live.

[krzysztofzelazko]

Having some free time I fixed your proposal, since I’ve made a few similar ones in the past. No need to thank me, have a nice week!

[b3hr4d]

Thank you so much for fixing the proposal, I really appreciate your help! Your experience with these proposals is invaluable . Wishing you a great week as well!