pull down to refresh

I completely agree with commitment to excellence and this is consistent with the intention of Flint. Like with any product development, there will be phases

  1. Private alpha (we're calling Kindling)
  2. Public beta (we're calling Firewood)
  3. GA (we're calling Blaze)

The level of quality you're speaking to for security and robustness definitely applies to #3 Blaze. For most applications, I would expect #3 to still require human programmers to review/audit/improve the code for proper attention to security, privacy, and scaling.

For #1 Kindling and #2 Firewood, pure vibecoding will be the norm to make it accessible to more people and to experiment and iterate in a more rapid fashion. For Kindling, like any alpha software, it is "tester beware" and hence there is encouragement to use small funds while testing.

use small funds while testing

There's a cool thing it is called testnet! It works very well for alpha!

reply
100 sats \ 1 reply \ @moneyball 9h

It actually doesn't. MDK, Lexe, LN, Spark, Ark, e-cash, etc. doesn't support it. Few wallets support it. Basically no one could test your apps. The goal here is to make it easy for people to test and rapid iteration.

reply
102 sats \ 0 replies \ @optimism 9h

I'm not entirely sure that it is true for everything you name there but no point in arguing. I'll put up some more infra for testnet, and make this constraint go away.

Any requests?

reply