Wen Polkadot???
There are far too many cases where projects receive funding from the treasury and then nothing comes of it.
I don’t believe anymore that they are working in good faith. We can make a write off of this 3m$.
The code is still available to be looked at here: GitHub · Where software is built
You’ll note that we’ve currently got 16 issues open and 40 closed. I’m sure for many of you who’ve not done software development on a browser though that progress doesn’t translate very well. I’ve got a video but I’m not authorized to upload here, so here’s a link: https://drive.google.com/file/d/1FcdniFm2tZNqqDkk2KTW_09EvSjZECAG/view?usp=sharing
Also, Polkadot Protocol Specification | Polkadot Protocol Specification is still not working. Who has access to fix this so that we can get the proper spec details to make sure what we’re implementing is working according to the spec? We’re flying blind here without docs and basically having to reverse engineer stuff.
This spec was mainly for node implementers and less for wallet developers.
@kdenhartog please ping me on github (@bkchr) in the issues where you need help and I will help you there. If wanted, we can also communicate in different ways or have a call or whatever.
@kdenhartog Fell free to update the community in case you are blocked.
Basti can help as shown above.
Parachain support is in progress now at the moment and should be code complete here soon. I’m working on reviewing the security of the pull requests of parachain support as well at the moment.
We did just realize there were some interop issues for AssetHub support as well that’s going to require a few minor changes to how we’re parsing and signing extrinsics to get supported as well.
In terms of issues that were blocking us, the engineering team has been tagging @bkchr a few times on Github. Thank you for the help on getting us unblocked.
Following Referendum 1412 (approved March 2025), the treasury committed ~3M USD for a full Brave Wallet integration with a 12-month delivery target (March 2026).
From the updates in this thread, the situation appears to reflect a pattern that is common in engineering-heavy environments: timelines are treated as flexible because technical complexity is inherently unpredictable.
However, from a governance perspective, that assumption is precisely what becomes problematic at treasury scale.
When funding is approved on a fixed-time, fixed-scope basis, delays should not be treated as an expected norm of execution — they should be treated as a deviation from the agreed conditions.
What we are seeing here is a gap between two models:
- an engineering-driven model where timelines naturally shift during implementation,
- and a treasury governance model that approved a time-bound deliverable under the assumption of predictable execution.
The issue is that only one of these models is currently being enforced in practice.
As a result:
- the 12-month commitment becomes non-binding in effect,
- delays carry no financial or structural consequence,
- and ecosystem capital absorbs execution uncertainty by default.
This is not about individual teams or competence. It is about whether OpenGov treats delivery timelines as real commitments or as approximate estimates that can slide without governance impact.
At the scale of Referendum 1412, that distinction matters.
Some of you may have seen Christian on our team mention this in the discord channel, but we’ve got Buy/Send/Swap support now working on asset hub in release.
Nightly and Beta all users have it enabled and we’re ramping up support for it on release to 100% over the next few weeks. It’s currently at 10%, but if you don’t see it enabled now, you can flag it on with brave://flags/#brave-wallet-polkadot (our progressive release will flag this on by default for more people as we go)
Next up, we’re working on adding a swap/bridging provider for polkadot as well, but I’m a bit concerned about the number of assets available (It looks like it’s mainly just USDT/USDC/DOT) with the potential provider so open to adding multiple if there’s recommendations from people here. Who do you primarily use?
I just finished with the security review for asset discovery and DApp support is coming after that.
Once we’ve got that in place, we’ll start running the NTT ads for this. I know people are upset that this took longer than our grant estimated. On the bright side, because we’ve been adding more users the ads will produce more impressions potentially converting more users.