Conversation

Notices

1. Hyolobrika (hyolobrika@social.fbxl.net)'s status on Friday, 22-Dec-2023 04:59:17 JST Hyolobrika
   How would digital currency programming with CBDCs be different from Bitcoin scripts and Ethereum smart contracts?
   • silverpill (silverpill@mitra.social)'s status on Friday, 22-Dec-2023 04:59:16 JST silverpill

     in reply to

     @Hyolobrika I don't think it will be very different. CBDC networks will be permissioned: only selected parties can deploy contacts and adjust spending conditions.

     Without strong privacy by default Bitcoin and Ethereum are losing fungibility and may end up in a similar state. CBDCs with extra steps.

   • silverpill (silverpill@mitra.social)'s status on Friday, 22-Dec-2023 06:25:11 JST silverpill

     in reply to

     @Hyolobrika As far as programming goes I don't expect any fundamental differences. An engineer writes some code, then it is executed by nodes of a network in a verifiable way.

     Permissioned may mean both things. In CBDC context it makes sense to strictly control who can run the nodes, and also who can create programs too (I expect banks will be allowed to create programs, but not ordinary people)

     >Also, do you have evidence for that?

     No, I didn't actually read any CBDC design documents. That's just my understanding of the goals and capabilities of those who create these systems.

   • Hyolobrika (hyolobrika@social.fbxl.net)'s status on Friday, 22-Dec-2023 06:25:12 JST Hyolobrika

     in reply to

     • silverpill

     CBDC networks will be permissioned: only selected parties can deploy contacts and adjust spending conditions.

     That sounds pretty different to me. With Bitcoin and Ethereum anyone can do that. Did you mean to write that you do think it will be different?

     Also, do you have evidence for that? I thought permissioned means that there is an approved set of nodes, not necessarily users that can deploy contracts.