Been experimenting with tap-to-bet functionality on prediction markets, but hitting some real friction points when it comes to implementation. Handling 87 different strikes for a single BTC price market is getting unwieldy—managing the liquidity pools and strike selection logic creates complexity that's trickier than it initially seemed. Looking for thoughts on best practices for streamlining multi-strike price markets without bloating the smart contract overhead.
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
11 Likes
Reward
11
9
Repost
Share
Comment
0/400
HappyMinerUncle
· 01-08 03:03
87 strikes is really outrageous. Why not consider layering or aggregation? It seems that just piling up will only make it slower and slower.
View OriginalReply0
probably_nothing_anon
· 01-07 14:13
Managing 87 strikes is really a nightmare... Why not just cut it down to 20 and give it a try?
View OriginalReply0
GateUser-e51e87c7
· 01-05 16:02
87 strikes are truly amazing. Handling so many liquidity pools at once must be incredibly crazy.
View OriginalReply0
rekt_but_not_broke
· 01-05 03:57
87 strikes directly take off, this architecture design is a bit weak.
View OriginalReply0
NeonCollector
· 01-05 03:53
Having 87 strikes is really a bit excessive. Why not just cut it in half and give it a try?
View OriginalReply0
StopLossMaster
· 01-05 03:50
87 strikes is really too exaggerated; if this continues, the contracts won't be able to run properly.
View OriginalReply0
GateUser-00be86fc
· 01-05 03:36
87 strikes really is a bit outrageous haha, if this keeps up, the gas fees will skyrocket.
View OriginalReply0
ContractTearjerker
· 01-05 03:35
87 strikes is really a nightmare, I think it needs to be handled in layers; otherwise, the contract size will definitely explode.
View OriginalReply0
DEXRobinHood
· 01-05 03:34
87 strikes is really outrageous. If this continues, gas fees will skyrocket. Why not try a layered aggregation solution instead?
Been experimenting with tap-to-bet functionality on prediction markets, but hitting some real friction points when it comes to implementation. Handling 87 different strikes for a single BTC price market is getting unwieldy—managing the liquidity pools and strike selection logic creates complexity that's trickier than it initially seemed. Looking for thoughts on best practices for streamlining multi-strike price markets without bloating the smart contract overhead.