Web3.js Jobs

I have a new Web3 idea ready to move from concept to code and I’m seeking an experienced blockchain developer to guide and build the entire solution with me. Because the project is still early-stage, I’m open on the specific chain, tech stack, and even the exact feature set—we’ll define those details together during an initial discovery call. What I do know is that the end product will rely on smart contracts, a dApp front end, and secure wallet interaction, so familiarity with Solidity or similar contract languages, , and modern front-end frameworks is essential. Here’s how I’d like to structure our collaboration: – First, a short technical workshop where you assess my concept, recommend an appropriate blockchain (Ethereum, BSC, Polkadot, or ...

I need someone to audit my token code I created with OpenZeppelin and AI? I implemented taxes and max wallet but I don't see taxes into my taxes wallets. I need someone to audit and maybe fix the issues and explain it. It is one hour of work I guess.

I’m assembling a freelance roster of seasoned Solana engineers to push a new decentralised application from idea to mainnet. The role centres on end-to-end DApp development: writing and auditing on-chain Rust programs, wiring them to a TypeScript/React front-end through Anchor or @solana/, and handling deployment, testing and optimisation so the final product is fast and fee-efficient. If you have shipped production Solana work before, please include links or GitHub repos that clearly show what you built and the parts you owned. I’ll review those examples first to decide who moves forward. We will work milestone-by-milestone; as soon as the initial scope is delivered (fully functional features, commented code, concise hand-off docs), I have follow-up tasks ready. Comfortable ...

I need someone experienced with OpenZeppelin and Taxes? The task is to add Taxes and Anti Whale functionality and create my BEP-20 token. I need something simple and working. Please apply only if you can show some tokens portfolio with at least 2 OpenZeppelin contracts.

I want to represent my physical gold holdings on the Binance Smart Chain by issuing a BEP-721 token. The contract must fully comply with the BEP-721 standard so wallets and marketplaces on BSC recognize it, yet go beyond the basics by including three essential capabilities: easy transferability, an on-chain dividend-distribution function that lets me send BNB or BUSD to current holders, and a burn mechanism I alone can trigger when underlying gold is redeemed. Please write clean, well-commented Solidity, test it thoroughly with Hardhat or Truffle, and deploy first to the BSC testnet; after I confirm everything works, walk me through the mainnet deployment. Deliverables 1. Auditable BEP-721 Solidity contract with transferability, dividend payments, and burn controls implemented. 2. Un...

Hi, I’m building a blockchain/Web3 project and I’m looking for a skilled blockchain developer who can help design and build the project using blockchain technology and Web3. I’d love to connect and explore a potential collaboration. Please let me know if you’re interested.

I'm looking for an experienced blockchain developer to create a smart contract on the Binance Smart Chain for a decentralized value proposition (DVP) platform. Essential requirements include: - Automated settlements - Asset transfer Ideal skills and experience: - Proficiency in BSC - Strong smart contract development skills - Experience with automated settlement mechanisms and asset transfer functionalities Please provide relevant past project experience and a timeline for completion.

I’m running the Flare Data Connector (FDC) client on a production-grade Mainnet node packaged in Docker. Since a recent configuration change, every submit2 call now returns: “Merkle root not available: attestation in consensus but not confirmed” I need a clean, permanent fix that restores normal Merkle-root confirmation on mainnet without breaking existing services. Scope • Inspect my current Dockerised setup, config files, and any recent edits I made. • Trace the submit2 flow inside the FDC client to locate the confirmation bottleneck. • Apply and test the patch so Merkle roots confirm as expected on mainnet. • Provide a concise write-up of what went wrong and how you resolved it, including any commands or code snippets I must keep ...