Twitxy Saved

Filament

@FilamentFinance

Exploring the future of trading through margin engines, LP designs and social behavior.

Creators of Filament Pro and @Flashduels.
Experimenting in the Lab flashduels.xyz Joined August 2023
1.2K Following 11K Followers 5.6K Posts

Latest posts 5

Filament @FilamentFinance
PSA: We will be discontinuing the frontend for Filament Pro on December 31, 2025.

Please claim your funds from Filament Pro at app(.)filament(.)finance

In case of any questions, please reach out @abhitejxyz through DM.
Filament @FilamentFinance Apr 24, 2025
Reminder of funds can be claimed at app.filament.finance.

As per our commitment to users, 100% funds for non-institutional are recovered.

In case of any questions or doubts, please reach out to us or tag @abhitejxyz.
View quoted post on X
2 replies 2 reposts 5 likes 3.5K views View on X
Filament @FilamentFinance
Prediction markets have been restrictive, one-off and favouring the capital - it changes w/ @Flashduels.
Abhitej | Bento.fun Verified account @abhitejxyz Aug 31, 2025
Testing @Flashduels Alpha on internal testnet.

What comes next:
> F1 auctions, followed by Football
> User-owned leagues
> Duels + Flash tournaments

Drop me a DM if you would live to be among the first cohort of users.

Not playing exclusivity game - simply DM so we can create a better feedback loop.
View quoted post on X
0 replies 0 reposts 5 likes 1.7K views View on X
Filament @FilamentFinance
Build, release, listen, iterate. Again and again.
Abhitej | Bento.fun Verified account @abhitejxyz Aug 7, 2025
Day 7/365: Building @FilamentFinance

Learning the hard way: Getting the product right in the first go is similar to winning the lottery on your first ticket.

It took us so many different products and product iterations to reach @Flashduels:

> Filament v0.5 - hit order scaling issue; hard to revamp the entire model
> Filament v1 - funding-borrowing rate harmony in OB-COMB pool hybrid was creating fee distribution issues
> Filament v1.2 - OB manipulation led to mapping edge case
> Built Run It Back -> fast games needed 1000s of users participating
> 60 seconds options - without the house; was hard to sustain
> Flashduels (Basic Binary Options) - wasn't needed by users
> Launchpad for Binary Options - no clear differentiation from prediction markets
> Binary Options for F1 - F1 caught attention, but the model felt complex

All of these iterations helped us gain better insights about users, products, and most importantly markets to tap into.

What works on paper rarely survives first contact with reality - liquidity cycles shift, market timing throws surprises, user behaviour doesn’t match assumptions. You realise quickly: the product isn’t something you figure out once - it’s something you uncover over time.

I’ve found myself stuck before fixated on one version of the product, one idea of how it should work. And honestly, that’s where progress stalled. I was busy pushing a car with square wheels, refusing to see there might be a better shape.

The breakthrough came not from a “perfect vision,” but from putting things out, observing real user behaviour, and doubling down on what worked even if it looked nothing like my original idea.

Iterations help you spot the sparks, let go of dead weight, and move closer to product-market fit - not in a straight line, but in responsive loops.

Every product that compounds eventually gets there through speed, feedback, and the humility to keep evolving.

Build, release, listen, iterate. Again and again.
View quoted post on X