You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reduce dependency on Horizon when developers only need to use the Friendbot faucet.
Currently, Friendbot is integrated into Horizon. By making it part of the RPC, developers could access Friendbot without needing to set up Horizon. This would allow contract developers to use Friendbot in local environments more easily. Additionally, it would enable us to ship Quickstart configurations with Horizon, RPC, or both, depending on the use case.
What would you like to see?
A Friendbot endpoint available via RPC.
The text was updated successfully, but these errors were encountered:
I suggest we keep friendbot independent of RPC, and instead consider what friendbot should be dependent on if not Horizon. The two options I see are RPC, or directly on stellar-core.
Why not build friendbot into RPC? Once upon a time friendbot was in Horizon, and it got split out into its own service, so at the least past us had reasons. Friendbot owns a series of accounts, but today RPC does not. It would be a new responsibility for RPC to manage accounts and not a new feature within existing responsibilities.
What problem does your feature solve?
Reduce dependency on Horizon when developers only need to use the Friendbot faucet.
Currently, Friendbot is integrated into Horizon. By making it part of the RPC, developers could access Friendbot without needing to set up Horizon. This would allow contract developers to use Friendbot in local environments more easily. Additionally, it would enable us to ship Quickstart configurations with Horizon, RPC, or both, depending on the use case.
What would you like to see?
A Friendbot endpoint available via RPC.
The text was updated successfully, but these errors were encountered: