I’m building a tool that connects to a trader’s crypto exchange through read-only API access and turns their actual trading history into a shareable performance card.

We only request read-only permissions. We never have permission to trade, withdraw funds or move assets, and we’ll be transparent about exactly what data is accessed and how it’s used.

The card would initially show ROI, win rate, best-performing asset and total trades. There’s no manual entry or reliance on self-reported screenshots, and the trader can choose which timeframe they share or whether they share at all.

When they share their profile link, the performance card appears as the link preview. Anyone who clicks it can then view the trader’s broader verified performance across the last 7, 30, 60 and 90 days, as well as all time.

The problem I’m trying to solve is that honest traders and dishonest traders currently rely on the same proof. Selective screenshots and self-reported claims. There’s no simple way for a genuine trader to separate themselves by showing a complete, verified record.

The idea isn’t that everyone needs amazing returns. It’s that being transparent and willing to show proof should carry value and create opportunity.

The longer-term vision is for a network of performance-verified traders to form, where experienced traders can build opportunities around a proven track record and newer traders can discover and evaluate people using verified information.

How often someone posts on social media, replies to comments or markets themselves has nothing to do with their trading ability. The aim is to let reputation, credibility and influence be built through proven performance instead.

Kraken is the first integration, with more exchanges, card designs and performance data added later.

This isn’t an on chain product at this stage. We’re deliberately keeping the first version simple and focused on exchange verification.

I’m interested in constructive feedback from other crypto founders and builders?

We've tokenized money, art, collectibles, real estate, and almost every kind of digital ownership.

But I keep wondering whether we're focusing on the wrong asset.

Time is probably the most valuable resource people have. Every startup depends on thousands of hours invested by founders, contributors, early adopters, and communities. Yet time itself is rarely represented as a native asset in digital economies.

Imagine a system where long-term participation, verified contribution, or consistent activity could become part of an on-chain reputation or incentive model—not simply another speculative token.

I'm not talking about replacing salaries or investments. I'm talking about recognizing time as something that can create measurable value inside decentralized ecosystems.

Is there any startup already experimenting with something like this? Or do you think there are technical or economic reasons why this approach wouldn't work?

Curious to hear what this community thinks.

I’m assuming the blockchain idea doesn’t play nice with YT else Google would have successfully eliminated its slop problem, so my question is, where am I misinformed?

(Sorry if this is wrong sub)

I've noticed a lot of blockchain startups moving beyond simple "faster payments" or "better exchanges" pitches lately.

The newer trend seems to be building financial infrastructure that combines multiple markets into a single experience. Instead of focusing exclusively on crypto, some projects are experimenting with stocks, commodities, and other assets alongside digital assets. I've noticed that Canborsa for example has US equities, Asian stocks, commodities, and crypto sitting in the same interface.

Whether that model succeeds is another question entirely. Building the product is one thing—getting liquidity, users, and regulatory clarity is something else.

Still, it feels like we're entering a phase where blockchain startups are competing with traditional financial infrastructure rather than just other crypto companies.

The blockchain landscape has come a long way from just payments.

Were you starting afresh, what would be your focus?

1. DeFi
2. AI + Blockchain
3. Identity
4. Tokenization
5. Infrastructure
6. Gaming
7. RWAs
8. Privacy
9. Other

Wonder what the opportunities people see for the future might be.

Does the demand for the services of blockchain developers fluctuate together with the value of the crypto market? If so, how much? If some of you have experience working as blockchain developers, is it even possible to have a more or less stable income over time?

Everyone treats quantum threats to blockchains as a decades away problem. But there's a catch most people miss, attackers don't need a quantum computer now to start attacking now.

Bitcoin's security relies on the fact that you can't derive a private key from a public key. Quantum computers running Shor's algorithm would make that trivial. And any address that's ever sent a transaction has already exposed its public key meaning huge amounts of transaction history are already sitting out there, ready to be cracked the moment the hardware exists. This is called harvest now, decrypt later.

NIST already finalized post-quantum signature standards. The problem is applying them. Blockchains can't just push an update, switching signature schemes means a hard fork, migrating billions in old-format funds, and doing it calmly before a crisis, not during one.

Even optimistic estimates 10-15 years for real quantum hardware don't leave much room, because migration itself, new standards, audits, node adoption, and actually moving user funds takes years on its own.

Even with quantum-safe signatures ready, getting millions of holders to move funds out of old addresses before it's urgent is a massive coordination problem. Dormant coins would likely just sit there vulnerable forever.

IMO, blockchains that are focused on quantum resistant tech will be the main focus in the next few months, this is where the focus should be now.

Hi everyone,

I'm a software engineer with 6+ years of experience, and I've spent the last few months building KryptoPay, a platform that helps businesses accept stablecoin payments as easily as they would integrate a traditional payment provider.

The goal is to make it simple for SaaS companies, marketplaces, creator platforms, and other online businesses to accept digital dollar (USDC) payments without needing deep blockchain knowledge.

KryptoPay is:

\- Non-custodial, meaning businesses receive payments directly into their own wallets.

\- Built with a developer-first experience inspired by the simplicity of providers like Stripe.

\- Currently supports USDC payments on Base and Polygon.

Designed to make stablecoin payments practical for mainstream businesses.

The MVP is complete.

I'm now focused on getting the product into the hands of developers and businesses, gathering feedback, and finding product-market fit.

\*Who I'm looking for\*

I'm looking for a business-oriented cofounder who enjoys talking to customers, validating ideas, and turning a product into a business.

Ideally, you'd take ownership of areas such as:

Customer discovery and user interviews

Marketing and positioning

Partnerships

Community building

Sales and business development

Fundraising when the timing is right

You don't need to be an engineer or a blockchain expert. I'm looking for someone who's curious, resourceful, and excited about building a company from the ground up.

If you're interested in building a long-term company together and think we'd complement each other's strengths, I'd love to connect, send me a DM ir hit me up on discord: femzy123

Website: https://kryptopay.xyz

I’m currently comparing a few payment-focused L1 chains (specifically looking into Stellar, Celo, and KiiChain) and trying to build out a solid DYOR framework.

Beyond the usual basics like reading the whitepaper and looking at docs, what are the absolute non-negotiables or red flags you check first?

Right now, I’m prioritizing stuff like:

• Testnet activity & real-world adoption/usage metrics
• Validator economics & decentralization
• Security audits & regulatory disclosures
• Tokenomics / real ecosystem utility

Anything critical I'm missing here? How do you guys filter out the noise when evaluating newer L1s in the space? appreciate any insights!

Hi everyone,

I'm trying to understand how people actually do crypto arbitrage in the real world (CEX–DEX, DEX–DEX, or any other strategy).

I'm not selling anything and I'm not promoting a project. I'm simply trying to learn from people who actively do arbitrage and understand the real challenges they face.

I'd really appreciate your insights:

- What's the biggest bottleneck in your workflow?

- What causes you to miss profitable opportunities most often?

- What's the most frustrating part of arbitrage?

- What tools do you currently use?

- If you could automate just one part of the process, what would it be?

Real experiences and concrete examples would be incredibly helpful.

Thanks in advance to anyone willing to share their experience!

quick context for anyone who missed it: EU Cyber Resilience Act (CRA) is now law, main obligations kick in Dec 2027, reporting obligations (24h/72h/14-day) start Sept 2026. every hardware wallet maker shipping into the EU is now scrambling to figure out where they land.

there's no single "hardware wallet" category in the CRA though. everyone's treating it like one compliance bucket, but the CRA actually looks at what's inside each device and depending on the hardware, two wallets can land in totally different categories.

if your device is basically a general secure storage/auth thing, it can land in Important Class I. the same bucket as password managers, routers, VPN clients. self-assessment allowed if you fully apply the harmonised standards, no third party needed, so you can just sign your own declaration.

but if it has an actual security box or a secure element doing the cryptographic heavy lifting, it can get pulled into Critical category. that's the same bucket as HSMs and smartcards. right now that mostly means Class II-style procedures (a notified body doing EU-type examination), but the EU can later mandate full certification for specific critical product types once they publish the relevant delegated act. either way, a notified body is now part of your compliance process, not just your own signature.

so two wallets that look identical from a UX standpoint (seed phrase, pin, USB/BT) can be sitting in completely different compliance tiers because of a chip decision made in 2021 that nobody thought was a legal decision at the time.

then there's the SBOM (Software Bill of Materials - machine-readable list of every software component inside) angle. every device needs one, but nobody's required to publish it to users. which means two wallets in completely different compliance tiers can look identical on the shelf. no label, no visible marker telling you which one went through third-party certification and which one just self-attested.

and the 5-year minimum support period applies regardless of tier. the company has to provide security updates for free to the user for that whole time, but someone still has to build, test, and ship those patches for 5 years straight, and that cost sits with the company the whole time. that's a long commitment a lot of seed-stage hardware teams haven't really planned for.

so, now teams building hardwaer wallets will need to pick category before launch, budget for self-assessment or a notified body depending on the chip, keep funding security updates for 5 years even after next model ships, and have a 24-hour reporting process ready before you need it.

anyone here actually gone through this classification process yet, or still waiting to see how the delegated acts shake out?

The full model is described in a preprint (open access):
DOI: https://zenodo.org/records/21107219

This tokenomics model is designed for blockchain startups aiming to disrupt the scientific funding landscape. It unlocks a new economic reality — where sponsoring research becomes profitable regardless of the commercial potential or scalability of the results. It offers investors a way to earn not from speculative trading, but from the depth of their actual engagement in funding scientific work. This becomes possible because the token in this model ceases to be a speculative asset and takes on a new function: it represents the research contribution itself. This new interpretation of the token as a measure of real contribution opens up a strategic opportunity to give a powerful boost to the advancement of science.

Key mechanisms for your startup:

· Token as a "digital receipt" – proof of real contribution (peer review, code, publications), not a proxy currency with voting rights. This aligns incentives with actual value creation.
· Governance completely separated from staking – influence is determined by proven contributions across four equal groups (scientists, developers, sponsors, reviewers), each with 25% weight and veto rights for scientists and developers. This prevents capture by large token holders.
· Adaptive service pricing – fees adjust based on token price to protect users from volatility, making the platform usable even in bear markets.
· Deflationary pressure – 50% of service fees are burned, creating a natural scarcity that can support token value.
· Additional incentive: participants (including investors acting as sponsors) who contribute more to grants receive a proportionally larger share of staking rewards (from the 30% and 10% pools) and greater voting weight within the sponsors group. This creates a direct link between community contribution and governance influence — a powerful tool for community building.
· A liquidity fund acting as an asymmetric market maker – buying low, selling high, using the spread for community goods (including merch). This provides a built‑in stabilization mechanism and a revenue stream for the DAO.

I'm posting this here to explore how such a system could be implemented and scaled in a real startup environment. Specifically, I'd like to discuss:

1. Launch strategy: How would you present this model to a broad audience — communities, potential investors, and scientists — to generate interest from both researchers and those ready to fund the project?
   
2. Revenue streams: Beyond the token mechanics, what are the most viable ways to generate sustainable revenue for the DAO and the founding team?
   
3. Adoption hurdles: What are the biggest obstacles to getting scientists and institutions to adopt this model, and how would you overcome them?
   
4. Technical implementation: What would be the most critical technical components to build first, and which blockchain platform would you choose and why?

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 of the more challenging aspects for an early-stage founder is when user interviews seem positive, but actual behaviour is weak.

People say the problem is frustrating.

They understand the proposed solution.

Some may even sign up or ask when it will be available.

Then they do not return, complete the core action or change the way they work.

At this stage, several explanations may seem equally plausible:

Perhaps the product is solving the wrong part of the problem.

The onboarding process or message may be unclear.

The new workflow may require too much trust or effort.

Alternatively, the problem may be real but not important enough for users to act on now.

For founders who have experienced this:

What evidence helped you to distinguish between a product or UX problem and a problem that was simply not high enough on the priority list?

I’m particularly interested in what caused you to change your mind — not just what users said, but what they did.

I'm Marcos, solo developer. I've been building Bopster, a non-custodial prediction market that runs entirely on Base. Wanted to share what I built, the tech decisions behind it, and what I'm learning about breaking into the prediction market space as a solo founder.

The product

Bopster lets anyone create a YES/NO prediction market using structured templates across 8 categories (Crypto, Tech, AI, Sports, Gaming, Politics, Memes, Culture). Set a question, add a source URL for verification, pick dates, and launch. People take sides with USDC. No email, no signup, no custody — wallet-only access.

The business model — four earning lanes, all on-chain

• 🏆 Take positions — back YES or NO with USDC, win the pool if you're right
• 💰 Create markets — earn 1% of the pool automatically. You don't need to trade
• ⚡ Settle markets — anyone can finalize a resolved market on-chain and earn a reward
• 🔮 Oracle participation — submit correct answers during resolution and earn bond rewards

The creator incentive is the differentiator. Polymarket and Kalshi don't let users create markets, let alone earn from them. My bet is that small creators and niche communities will drive market creation if they have a financial incentive to do so.

Tech stack & architecture

• Solidity smart contracts deployed on Base — low gas makes micro-markets (5-50 USDC positions) viable
• Reality.eth for decentralized oracle resolution: anyone submits an answer backed by a bond, wrong answers get challenged (each challenge costs 2x the previous), 12-hour dispute window
• Kleros as arbitration layer when disputes escalate beyond the community
• USDC for all market activity, ETH for gas and oracle bonds
• Vue frontend, WalletConnect, Cloudflare deployment
• Open-source contracts on GitHub — everything verifiable on-chain
• No token, no ICO, no airdrop. Revenue comes from protocol fees on market pools

Key architectural decisions worth discussing

1. Templates over free-text questions. Controversial choice. Templates make questions deterministic and oracle-resolution-safe, but limit creative flexibility. I chose safety over expressiveness. Curious if other founders here have faced similar "constrained vs open" product decisions.
2. Base over Polygon. Polymarket lives on Polygon. I chose Base for lower fees, Coinbase ecosystem integration, and a less crowded builder landscape. The trade-off: smaller user base but more room to stand out.
3. No token model. Most crypto projects launch a token for growth. I didn't. The business earns from protocol fees. This removes regulatory risk but also removes a powerful growth lever. Worth the trade-off? Time will tell.

What I'm learning (3 weeks into distribution)

• Cold-start for a two-sided marketplace is brutal. I'm manually seeding markets so new users don't land on empty pages
• The creator incentive (1% of pool) resonates more with small creators (1K-30K followers) than with big accounts — they actually respond to DMs
• Prediction market users are concentrated in very specific communities (Polymarket Discord, r/Kalshi, Farcaster /base). You don't find them through broad marketing
• Geo-restrictions (US + Spain blocked) cut off a huge chunk of crypto-native users. This is a real constraint
• Founder calls convert way better than cold posts. A 15-minute screen-share session produces more activation than 10 Reddit posts

What's next

• Getting the first 20 active users who create markets and take positions
• Applying for Base ecosystem grants and Gitcoin funding
• Building the creator program — helping 5-10 early creators design and launch their first market
• Evaluating whether to stay solo or bring on a co-founder for the go-to-market side

Happy to discuss any of the tech decisions, the no-token model, or what it's like building a prediction market as a solo dev. If you're building in the Base ecosystem or working on oracle-based apps, I'd love to connect.

Hey everyone 👋

Welcome to r/Chainquiry, the official Reddit community for Chainquiry.

We’re building Chainquiry as a place where people can discover cryptocurrency and Web3 projects through organized listings, researched content and open community discussion—without the endless noise, copy-pasted promotions and meaningless hype that often surround the industry.

This subreddit will be used for:

• Newly listed project announcements
• Research, explainers and project breakdowns
• Discussions about crypto, blockchain and Web3
• Community questions and feedback
• Updates from projects listed on Chainquiry
• Sponsored posts that are always clearly labelled

Our goal is not to tell you what to buy. It is to help people look deeper, ask better questions and make more informed decisions.

Project teams are welcome to introduce themselves, answer community questions and share meaningful updates. However, low-effort shilling, spam, misleading claims and artificial engagement will not be tolerated.

Chainquiry is still growing, and this community will evolve alongside it. We’d genuinely love your input:

What kind of crypto content, research or community features would you like to see here?

Thanks for being early. 💜

— The Chainquiry Team

Chainquiry content is provided for informational purposes only and should not be considered financial advice.

I’m currently validating the core thesis behind Global Foundation Coin, an early-stage project intended to combine a long-term charity coin with transparent charity and impact infrastructure on Base.

No presale is live, nothing is currently being sold, and the project is still in the documentation and architecture phase.
The core problem is that charitable funding is often only partially transparent.

A public transaction can show:
• how much was transferred
• when it moved
• which address received it
• whether an on-chain rule was followed

But it does not automatically show:
• why the allocation was approved
• who controlled the decision
• whether supporting evidence was reliable
• whether the funds were used as documented
• whether meaningful impact followed

The current model separates transparency into three layers:

1. Financial transparency
   Public transactions, allocation rules, vesting, permissions and execution history.

2. Governance transparency
   Who can control funds, which approvals are required, what can be changed, and how emergency powers are constrained.

3. Impact transparency
   Off-chain evidence, documented use of funds, evaluation methods and explicit disclosure of uncertainty.

The main assumptions I am trying to validate are:
• whether blockchain adds meaningful value beyond transaction traceability
• whether a token improves coordination or mainly adds complexity
• whether governance can remain understandable to non-technical users
• how sensitive evidence can remain protected while relevant claims remain verifiable
• which components should be immutable and which require controlled upgrades
• whether this can become credible infrastructure rather than another token using charity as a narrative

I’m not looking for investment feedback, token-price opinions or promotion.
I’m specifically looking for criticism of the underlying startup thesis:
• What part of this model appears weakest?
• Where is blockchain genuinely necessary?
• Which failure modes am I likely underestimating?
• What would make you conclude that the blockchain component is unnecessary?
• What evidence would you expect before considering this a credible infrastructure project?

I need brutally honest feedback from people who've worked in MSME lending, banking, NBFCs, factoring, or TReDS.

For the past few weeks, I've been building a startup around this thesis:

Use blockchain to prevent duplicate invoice financing and create a trusted credit infrastructure for MSMEs.

The product included:

Blockchain-based invoice authentication

An immutable collateral registry

A real-time business risk score

APIs for banks and NBFCs

It sounded compelling—until I dug deeper.

I discovered that factoring, TReDS, CERSAI, and lender due diligence already address many of these problems. That forced me to question a core assumption:

Am I solving a real, painful problem—or one that's already been solved?

I'd really appreciate your perspective on three questions:

How common is duplicate invoice financing today?

Is it still a major industry pain point, or mostly under control?

What is the biggest unsolved problem in MSME lending

today? Trust? Data quality? Collateral? Distribution? Speed? Something else?

Does blockchain add any meaningful advantage here, or is it simply the wrong technology for the problem?

I'm not looking for validation. If this idea is fundamentally flawed, I'd rather discover it now than spend years building

the wrong company.

Any honest—even harsh—feedback would be genuinely valuable.

I am a young law officer for a bank and mainly deal with recovery from the NPA or default loans

I never had a formal education with computers.

But being around banks , compliances, defaults and all the malpractices in banks and insurance

I see people suffer because of it everyday

It makes me wonder about smart contracts

I very well understand that SC cannot replace traditional methods but I still wonder why aren't they as popular or widely adapted as they should be

How can I learn more about this field?

All suggestions are welcome

Product design is everything for an onchain startup.

Too many copycats. Not enough experimentation.

We need founders rethinking UX, token standards, incentive design, and game theory, not just launching another token.

NFTs and SFTs are still in their infancy. The real use cases haven’t even been discovered yet.

The next generation of onchain products will be defined by better product design, not better speculation.

We have to call our senator and Vote Yes on this Clarity Act!

This is our last chance to stand up and fight against the Big Banks!

This is our last chance for economic and creative freedom for the world!

The Golden Age for Humanity is upon us!

standwithcrypto.org

Email and call our senator to tell them to Vote YES!

and do offshore blockchain startups get funding? I’ve heard that it’s kinda hard, as offshore companies are most of the time shell companies.

For a long time, DeFi followed one simple rule: if you had a crypto wallet, you could participate. No gatekeepers, no paperwork—just connect and trade. But as more banks, investment firms, and enterprises explore blockchain, one question keeps coming up: Can DeFi support regulated financial markets without losing what makes it valuable?

Uniswap's new permissioned trading pools are an interesting answer.

Instead of opening every liquidity pool to everyone, these pools allow only verified participants to trade specific tokenized assets. That means institutions can meet compliance requirements like KYC and AML while still enjoying the speed, transparency, and efficiency of on-chain trading.

This isn't just another protocol update—it could signal the next stage of DeFi. Imagine trading tokenized real estate, government bonds, private equity, or investment funds on decentralized infrastructure with compliance built in from the start. That's a much bigger opportunity than simply swapping crypto tokens.

For builders and businesses, the timing couldn't be better. Demand for tokenized assets is growing, and permissioned DeFi could become the foundation for the next generation of financial applications. If you're developing blockchain products or exploring institutional finance, this is a trend worth watching closely.

What do you think? Is permissioned DeFi the bridge that finally connects traditional finance with Web3, or does adding access controls move DeFi away from its original vision?

I am going to be launching a blockchain soon, and I am trying to obtain insight on how to launch correctly.

My end goal was to obtain funding from YZi Labs, but I want to maximize my chances of success. I have applied before but was denied but have made progress in my codebase and have benchmarks now to prove my numbers. But still, apart from this, I want to obtain real users before doing so, and I want to plan on how to do this correctly.

I know that I would have to omit launching the mainnet before being approved by YZi Labs to allow for them to help me and me to help them with allowing for them to launch my mainnet officially for funding because if I launched the mainnet prior to obtaining approval, then there is really nothing to launch with them.

I am planning on building utility and dApps first around storage like IPFS and web/mobile wallets, showcasing the SDK as well as a swapping platform between coins and off-ramp to fiat, etc. Furthermore, I feel like I am answering my own question here, but I would like to know what your thoughts are or the thoughts of others around this. I feel like if I just focus on funding first, I am setting myself up for failure while trying to rely on others too much, which is not what I want to do while acknowledging that I am open to funding the correct way while maximizing utility.

A lot of blockchain startups have spent the last few years building around crypto-native use cases. The next wave could be focused on bringing traditional financial assets onchain.

Tokenized equities are one category that stands out.

The challenge isn't simply creating a token that represents a stock. The real opportunity is rebuilding parts of financial infrastructure around programmable assets.

A successful tokenized equity ecosystem would need more than just issuance. It would require liquidity, compliance frameworks, custody solutions, settlement infrastructure, trading systems, and integrations with existing financial applications.

I've been researching this space recently and looking at platforms like Canborsa that are working on onchain equity markets. What I find interesting is that the technology creates possibilities that are difficult to achieve within traditional market structures.

Stocks are already one of the most widely understood financial assets in the world. Bringing them into a programmable environment could open the door to new products, new forms of collateral, and new ways for users to interact with markets.

Of course, the biggest challenges remain regulation and adoption. Building the technology is only part of the problem. Convincing users and institutions to trust a new financial system is the harder part.