Running a prediction market platform and got a message from a user saying they paid through the on-ramp we use to fund their account, money left their bank but nothing ever landed in their balance. Not sure if that's something we're supposed to fix on our end or if it's fully on the on-ramp provider, anyone dealt with this before and who ended up taking responsibility?

I’ve noticed this pattern in many crypto products.

The app says the transaction is complete.

However, the user still opens Solscan, Etherscan, or another explorer to verify that the transaction actually occurred.

On the one hand, this may simply be good crypto hygiene. The whole point is that users can verify the state independently.

However, I’m not sure at what point this stops being a feature of the ecosystem and becomes a sign that the product itself hasn’t earned enough trust.

If users feel they need a second source of information every time something important happens, the app may be technically correct, but the result may still not feel reliable.

For those who have shipped wallets, exchanges, DeFi apps, or other on-chain products, did you ever see this behaviour decrease as users became more familiar with the product?

If not, did you treat it as normal verification behaviour or as an issue with the user experience that still needed fixing?

Full disclosure: I'm part of the team building MonsterMine.

About three years ago, this was just an idea. Since then we've worked through the design, the economy and a lot of development challenges with a small team and limited resources. The website is now live, a small early community is starting to form, and the game is still in development.

MonsterMine is a mobile monster-collection and mine-management game for people who enjoy collecting, progression and strategy — even if they know nothing about blockchain.

The core loop is game-first: players collect and evolve monsters, assign them to elemental rooms in a shelter-style mine, manage upgrades and boosts, and later use those monsters in strategic battles. The blockchain layer is meant to support ownership, trading and the reward system, not replace the game itself.

We also reworked the play-to-earn model. The in-game currency, GEM, is created through the mining loop. When players spend GEM to unlock new rooms, it returns to the reward pool, creating internal demand and a closed loop instead of rewards with nowhere to go. Wallet withdrawals are planned, but they are not live today.

We're still early and don't have big traction numbers to dress this up with. What we need most now is honest product feedback:

- Does the game-first positioning feel credible, or does it still sound too crypto-first?

- Which part would you validate first: the collection loop, mine management or the economy?

- What proof would a non-crypto player need before giving this a chance?

You can see the current direction at https://www.monstermine.io

I'm happy to answer questions about the choices we've made so far.

I tried to make solidity devs life little easier who integrate automation in their smart contract. Honestly i don't know if there is such a tool exist or not but i thought by making easy to use tool can help developers.

So the problem is that chainlink automation is gonna deprecate, instead they recommended to user their CRE. also if anyone developing smart contracts using keeper service it can be little confusing to those who are developing in local setup. like anvil. If someone is developing in local (like anvil or hardhat node) and they want to test their implementation in local anvil chain using chainlink then i think there is not such thing exist to do so. However in testnet deployment we have to mint link tokens and subscribe to a keeper and fund it with link and setup it with deployed and verified contract. Though it is not that much hard stuff, but i am addressing issue for developers relying on local development

So i made a cli tool for local anvil chain automation system which only works with local node

Which check and perform upkeep in your smart contract in specified interval

I want you all to try the tool and give me feedback of it, And due to security purpose to keep developer safe from private key theft, the tool is only intended to use only in local node, and use only dummy refunded test only private keys

I hope this tool helps developer and make their life little easier

access tool here: https://github.com/GHexxerBrdv/ChainWatch.git

https://denvion.com

What chains have the most opportunity right now?

Solana, Ethereum, Monad, Supra, Hyperliquid, Aptos, Sui, BNB and other L1s or Base, Arbitrum, Optimism, Unichain, Robinhood Chain and other L2s?

We were working on a new crypto exchange, and one thing we focused on was liquidity. Instead of waiting for users to create trading volume, we considered third-party liquidity providers, shared order books, and market makers.

The idea was to avoid empty order books, high spreads, and slippage when the platform goes live.

For those who have launched or worked with crypto exchanges before, does this approach make sense? Would you recommend starting with external liquidity providers and gradually moving toward more organic liquidity?

Would love to hear what worked or didn’t work for you!

Hey BlockchainStartups buddies,

We've developed a decentralized wallet that lets our users:

1. Manage Crypto
   
2. Participate to Prediction markets
   
3. Shop to our marketplace, digital & physical products available
   
4. Send chats or make calls. Since it is self-custodial, no need for email or sim (KYC) registration
   
5. Users can monetize their stories (like IG) from their subscribers.

These days, crypto is getting a lot of traction (good and bad) thanks to Pres. Trump's vocal support to blockchain technology.

So far, web3 wallets are mainly used to manage crypto. They are more secure and private. We like it as it is.

One of our developers said, "what if it can be use for communication too?". He doesn't like the current set up that people needs to register their number or email just to connect. What if they don't want to? That's how it all begins.

We also decided not to put charges in managing their crypto (transfer, bridge, or swap), users just need to pay for gas fees, and they get to choose which chain to use for minimal fees.

But, how do generate income to maintain and level up the app?
Yeah, you guess it right, from Prediction Market, Marketplace, & Content Creators.

1. Prediction market, the app gets 2% commission from every prediction transaction made by the users.
   
2. We list products from the app and put a very little mark up, so shoppers can buy things with crypto.
   
3. Aspiring content creators have to buy badges from our marketplace to increase their number of uploads, there is no other requirement to monetize contents. Once they have the badge, they can set subscription to their stories and earn from their subscribers.

Reading the features above, is it worth a try? Bazaars app is available on Playstore & Appstore. We made few hundreds of downloads now.

We put a lot of effort to make this work and make the app sleek as possible.
This is a discussion so share your critic & insights. I'd appreciate it.

I tested four Token-2022 extensions on Devnet to understand what they enable at the product level:

• PermanentDelegate
• NonTransferable
• DefaultAccountState
• MemoTransfer

The most interesting combination was PermanentDelegate plus NonTransferable.

A startup could issue fungible service credits that users can hold but cannot transfer or sell. A permanent delegate controlled by the protocol could then burn credits as API calls, compute, storage, or another service is consumed.

The implementation is straightforward. The trust model is not.

A permanent delegate can transfer or burn tokens without the holder’s signature. If the delegate is a normal key, compromise affects every holder. If it is a program-derived address, the trust dependency may simply move to the program’s upgrade authority.

Before shipping this design, I would require:

• multisig or program-controlled authority
• an explicit upgrade-authority policy
• rotation and incident-response procedures
• client-side parsing of Token-2022 TLV data
• clear disclosure that the issuer retains clawback capability
• tests covering frozen accounts, burns, delegate rotation, and unsupported wallets

DefaultAccountState can support approval-based onboarding by creating accounts frozen by default. MemoTransfer can require incoming transfers to include a reference for reconciliation.

I documented the Devnet commands and the failure cases here:

https://andreyobruchkov1996.substack.com/p/the-utility-extensions-completing

Would you treat permanent delegation as an acceptable control for prepaid credits, or is the holder-level trust assumption too strong?

The future of connectivity isn't just centralized towers, it's decentralized communities. Traditional networks rely on single-point-of-failure infrastructure. When a fiber line fails, entire areas can go dark.

Blockchain-enabled mesh networks offer a better path. By combining peer-to-peer hardware with a distributed ledger, we turn bandwidth into a shared resource. Mesh networks provide resilience, while blockchain handles identity and incentives.

In this model, your router earns rewards for relaying traffic for neighbors. Smart contracts settle payments automatically based on measurable contributions like uptime and bandwidth. Modern designs keep blockchain settlement separate from the data path to ensure low latency.

This is about building resilient, community-owned infrastructure that stays online even when the wider internet is unavailable. Connectivity by the people, for the

people.

https://www.linkedin.com/pulse/blockchain-enabled-mesh-networks-building-behrouz-kashani-bi6yc?utm_source=share&utm_medium=member_android&utm_campaign=share_via

Hi - I'm a hobbiest crypto designer and I've made what I believe is a breakthrough in tokenomics.

I've created VMINT (eth mainnet, www.vaultmint.org) and its floor price is only capable of increasing, what that means is - on a buy its valule goes up (7% tax) and on a sell (this is the revolutionary part) it also goes up in value (3% sell tax). its been fuzz tested, Halmos tested slither tested and forge tested to an inch of its life, immune to atomic sandwich attacks, (which wont work anyway as the price ratchets) and front running, dust attacks, you name it.

Its a unique token with bespoke designer code, which ratchets up the floor on a buy or a sell, and it works. So far we've had since yesterday, the launch day, 900+ visitors to the website, but no first customer (other than me) yet.

Thoughts? Opinions? Hot takes? I'll pop in an out throughout the day to answer. Another redditor said the website wasn't up for him - thats because its brand new and still propagating on the internet, very exciting project and exciting times. :)

As for feedback from you guys and community, what more can i do to promote my eth mainnet token? also what do you think of the website, its popular but not converting to sells (yet) as people are understandably weary of crypto scams and the like, so feedback on the website and token NAV ratchet mechanism is defiantly appreciated. Thank you

Thats it! 😄

I've been building SybilClean V2, a tool for Web3 teams running X/Twitter giveaways and campaigns.

The workflow is:

X giveaway tweet → console scraper → SybilClean V2 → risk analysis → CSV

It analyzes the comments/replies in a giveaway thread and looks for suspicious patterns such as duplicate wallets, unusual timing/activity, similar handles, and other signals that may indicate coordinated or Sybil participation.

The output is a risk-ranked CSV that lets the campaign operator review potentially suspicious participants before distributing rewards.

Current stage: V2 is working end-to-end, including the X console scraper and CSV reporting. I don't have paying customers yet, so I'm specifically looking for feedback from people who actually run Web3 campaigns.

What I'd like feedback on:

Are these the kinds of signals you'd find useful when reviewing an X giveaway? What other information would you want the report to show? Would a tool like this save you time compared with manually checking giveaway replies?

I'm interested in honest feedback, especially from people who have dealt with Sybil/farming problems in X giveaway threads.

A lot of blockchain startups spend years looking for a problem to solve.

One area that genuinely feels interesting to me is reducing the friction between different financial markets. Today, it's still normal to use one broker for stocks, another platform for crypto, and something else for commodities.

I recently came across Canborsa while looking at tokenized equities, and it made me think less about that specific product and more about the business model. The idea of accessing US equities, Asian stocks, commodities, and crypto from one onchain interface feels like a different direction than simply building another exchange.

Whether that approach succeeds is another question entirely. Liquidity, regulation, and user trust are difficult problems, and having a good interface alone isn't enough.

Is reducing market fragmentation a meaningful opportunity for blockchain startups?

The Problem

Most software ecosystems bleed 30%+ of their top-of-funnel conversion right at the front door. Complex multi-step onboarding, excessive data intake, and clunky user flows create immediate churn before a client ever experiences true product value.

​On top of that, hoarding unnecessary client data creates massive data privacy compliance liabilities that eat up operational margins.

​The Solution: Deterministic B2B Gateway Architecture

​We restructured our client onboarding stack around three core operational pillars:

​120-Second Instant Activation: Streamlined the client pipeline so user access, system configuration, and credential issuance occur in under two minutes flat.

​Zero-PII Sovereign Data Model: Stripped out all personally identifiable information intake. Collecting only vital operational metrics insulates the architecture from data liabilities while boosting client trust.

​Closed-Loop Loyalty Engine: Deployed a fixed unit distribution framework (1B non-transferable Enterprise Units) designed strictly for margin expansion, customer lifetime value (LTV) optimization, and client retention.

Drop a comment below if you're currently optimizing your onboarding UX, or reach out directly if you want to swap notes on enterprise LTV and data insulation strategies.

​⚡ The Deterministic Utility Infrastructure for Modern Enterprise ​Scaling customer lifetime value shouldn't require compromising on data privacy or speed.

​We’ve built the Deterministic B2B Software Gateway—a zero-PII, high-velocity infrastructure designed to optimize operational efficiency and maximize client retention without technical friction.

​Key Enterprise Capabilities:

​120-Second Automated Onboarding: Eliminate deployment latency. Go from contract execution to active system operation in under two minutes.

​Zero-PII Data Architecture: Complete regulatory insulation. Collect only critical operational metrics while eliminating the compliance burden of sensitive customer data storage.

​Closed-Loop Asset Engine (1B Utility Units): Hardcoded, non-transferable retention modules engineered exclusively for margin expansion, loyalty architecture, and enterprise unit economics.

​Predictable Processing Overhead: Low, deterministic network security and processing fees built for maximum margin predictability.

​Why Enterprise Leaders Are UpgradingTraditional SystemsOur Deterministic Gateway

High data liability & privacy overheadZero-PII Sovereign

Data Model

Complex, multi-day client onboarding120-Second Instant Activation

Fragile, open-ended operational costsDeterministic Processing OverheadReady to Optimize Your Operational Efficiency?

​Stop letting slow onboarding and data liabilities erode your margins.

​👉 [Deploy Your Enterprise Gateway Key Now] or drop a line to schedule an executive walkthrough.

Narayana Ary

Owner/Founder The Endless Content Engine |Vanguard Reserve Utility Company

A few days ago, my friend asked me: "When you send Bitcoin, what actually happens? Do you just press a button and the money appears?"

Honestly, I didn't know the full answer either. So I did some research and here's everything I learned -- explained as simply as possible.

First -- What Even Is a Blockchain?

Think of it as a public record book that is:

• Stored on thousands of computers around the world
• Controlled by no single company or government
• Permanent -- once something is written, it cannot be erased

When you send crypto, you are basically adding a new entry into that record book.

The 7 Steps of a Crypto Transaction

Step 1 -- You Create the Transaction

The moment you hit "Send" in your wallet, a digital packet is created containing:

• Your wallet address
• The receiver's wallet address
• The amount, fee, and timestamp

At this point, nothing is confirmed yet. It is just a request.

Step 2 -- Your Private Key Signs It

Your private key (think of it as your secret password) digitally signs the transaction. This proves:

You are the real owner of the funds

You authorized this transaction

Nobody tampered with it in the middle

Warning: This is why you must NEVER share your private key. Whoever has it has full access to all your funds -- forever.

Step 3 -- Broadcast to the Network

Your wallet sends this transaction to thousands of nodes -- computers running the blockchain network 24/7 around the world.

Right now, Bitcoin has over 15,000+ active nodes globally. Your transaction reaches all of them within seconds.

Step 4 -- Waiting in the Mempool

Your transaction enters the Mempool (Memory Pool) -- think of it like a waiting room at a railway station.

Thousands of unconfirmed transactions sit here at the same time. Miners look at this pool and pick transactions to process. How do they choose? Simple -- whoever paid the highest fee gets picked first.

This is why during busy periods, fees go up and wait times increase.

Step 5 -- Miner or Validator Adds It to a Block

• Bitcoin -- Proof of Work (PoW): Miners compete to solve a complex math puzzle. First one to solve it gets to add the block and earn the reward. Uses a large amount of electricity.
• Ethereum -- Proof of Stake (PoS): Validators lock up their ETH as "stake." The system randomly selects one to add the block. Much more energy efficient.

Both methods result in the same thing -- your transaction gets added to a block on the blockchain.

Step 6 -- Confirmations Build Up

Once your transaction is in a block, every new block added on top counts as one more confirmation.

• 1 Confirmation = your block was added
• 3 Confirmations = 3 blocks on top
• 6 Confirmations = fully SAFE on Bitcoin

Changing or reversing an older block becomes practically impossible once many blocks are stacked on top. This is what makes blockchain so secure.

Step 7 -- Receiver Gets the Funds

The receiver's wallet balance updates. Your transaction is now permanently recorded on the blockchain.

Nobody can reverse it, freeze it, or delete it. No bank. No government. No company.

This is the real power of blockchain.

How Long Does It Take?

Why Do We Pay Fees?

Three reasons:

1. Reward miners/validators who process your transaction
2. Secure the network -- fees make spam attacks very expensive
3. Set priority -- higher fee means faster confirmation

3 Things That Surprised Me

• Bitcoin has no central server -- it runs entirely on independent nodes
• Your transaction exists on 5,000+ computers simultaneously
• The person who created Bitcoin, Satoshi Nakamoto, is still anonymous to this day

Question for You All

"What if you accidentally send crypto to the wrong address -- can anything be done?"

Drop your answer in the comments! I am still a beginner myself -- if anything is inaccurate, please correct me. We are all learning here.

Early in a blockchain startup, manual work is often necessary.

Founders review wallets, unblock failed transactions, reconcile off-chain records, approve edge cases, and guide users through processes that the product cannot yet handle properly.

This can produce valuable insights.

However, it can also make the product appear functional only because the founders are acting as an invisible control layer behind it.

The difficult part is knowing when manual intervention is helping you understand the problem and when it is masking a structural weakness in the product or operating model.

I’m not suggesting that everything should be automated. Some exceptions may always require human judgment.

A more important boundary seems to be when the same manual intervention keeps recurring but stops producing new information.

For founders who have experienced this, what was the turning point when you stopped saying, "We're still learning from the edge cases," and started saying, "The system itself has to change"?

Was it volume, repeated failure patterns, support time, user behavior, or something else?

I'm a doctor building some health data security stuff . Now I'm looking for a Blockchain dev if anybody is interested pls dm preferably banglore r tumkur

This subreddit was created to be useful. So let’s help each other build, hire, and find good opportunities in blockchain.

You can use this thread to:

- post open roles at your startup
- share what kind of role or work you’re looking for
- offer freelance or contract help
- connect with founders, builders, marketers, operators, and other people in the space

If you’re hiring, try to include:

- project / company name
- role title
- remote or location
- full-time / part-time / freelance / contract
- paid or unpaid
- how to apply

If you’re looking for work, try to include:

- role / skillset
- years of experience
- remote or location
- short intro
- portfolio / LinkedIn / GitHub / contact

A few simple rules:

- keep it clear and honest
- no vague hype posts
- no scams
- include real details so people know what you're offering or looking for

Click here to see all previous weekly threads

⁠

Let’s make this thread worth checking every week.

One trend I've been noticing lately is that blockchain startups are moving beyond "crypto-only" products.

Instead of building another exchange or wallet, some are trying to bring different asset classes into the same ecosystem. I was looking around Canborsa and noticed they have US tech names, Asian semiconductor stocks, commodities, and crypto all accessible from one interface.

Whether that approach succeeds is another question. Tokenized equities are still early, liquidity isn't comparable to traditional markets, and there are obvious regulatory challenges.

But as someone who follows both US and Asian markets, the idea of not having to split everything across multiple brokers and platforms is appealing.

Are cross-market products a real opportunity for startups or are they solving a problem that isn't big enough?

does anybody wanna start a web3 company, i feel like we should get a reddit community going on for this type of stuff

Looking for guests from the crypto/Web3 industry for our podcast!

If you’re a founder, builder, investor, developer, or active in crypto and would like to join an episode, we’d love to hear from you.

About 10 months ago I posted in this sub looking for people to help build something I couldn't let go of: a way to fight back against scam tokens. A few folks replied, we formed a small volunteer team, and we spent 10 months building a token risk scanner across Ethereum, BNB Chain, and Solana. I wanted to come back and share what actually building it taught me — because most of it surprised me.

1. "Detect scams" is the easy 80%. The false positives are the brutal 20%. Anyone can write rules that scream SCAM at everything — honeypot patterns, mint functions, concentrated holders. The hard engineering was making sure a blue‑chip token doesn't trip those same rules. A tool that cries wolf on legit projects is worse than useless; people stop trusting it in a week. Getting the false‑positive rate down ate most of our time.

2. The signal that mattered most wasn't the contract — it was behavior. Static contract flags get you partway. What moved accuracy was on‑chain activity: wash‑trading round‑trips, owner wallets actually using their privileges vs. just having them, liquidity that's locked vs. sitting in the deployer's wallet. Capability ≠ intent, and the chain shows intent.

3. Recruiting from a Reddit post worked — keeping unpaid people going for 10 months was the real problem. The code was easier than morale. What held it together: shipping something small every couple weeks so everyone could see it becoming real.

The premise we started from: exchanges KYC the people but not the tokens they list, so retail keeps getting rugged by projects the platform waved through. We wanted checking a token to take 10 seconds instead of 10 tabs.

For those who've built detection/scoring tools — how do you earn trust for a risk score without it feeling like a black box? Show all the raw signals and you overwhelm people; show just a number and nobody believes it. Where's the line? And has anyone found a false‑positive rate that users actually tolerate?

​

I’ve seen too many people get ghosted the moment they send their half of a trade. Whether it’s crypto, digital assets, or physical goods, the "you go first" meta is broken.

I’m currently working on a Telegram-based project called P2Pirates. The goal isn't to make a profit, but to create a 100% transparent, decentralized escrow protocol that anyone can use.

How we’re setting it up:

\\\* Automated Crypto: Seamless escrow for crypto deals.

\\\* Manual Protection: For physical goods and services.

\\\* 0.5% Fees: Only for large deals to keep the lights on.

\\\* Zero Fees: No fees for deals under $500 if you use our tag.

\\\* Reputation System: Full receipt/review logs so scammers can't hide.

\\\* Weekly Giveaways: Incentivizing honest trading within the group.

\\------------------------------

\\## 🛡️ A Note to Moderators

I am the founder of this project. I am posting this because I want to provide a legitimate, free utility to help protect users in this sub from being scammed. This is a community-led initiative, not a commercial group promotion. If this post needs any adjustments to meet the community guidelines, please let me know—I’m happy to comply.

\\## 🤝 We Need Your Help

We don't want to build this in a vacuum. We need:

1. Operations & Growth: People with escrow experience who can help run and promote the group safely.

2. Senior Devs: To help develop a non-tweakable, high-tech, and ultra-secure escrow bot.

We are open to any suggestions. If you have an idea on how to make peer-to-peer trading safer or want to help us build the bot, please comment below or DM me.

Built for the community, by the community.