[GNC] Bitcoin Lightning payments

[HSC]

> ------------------------------
> 

> Message: 2
> Date: Sun, 19 Jun 2022 15:02:33 +0100
> From: "Dr. David Kirkby" drkirkby at kirkbymicrowave.co.uk
> 

> To: Peter West pbw at pbw.id.au
> 

> Cc: gnucash-user at gnucash.org, stepbystepfarm at comcast.net
> Subject: Re: [GNC] Bitcoin Lightning payments
> Message-ID:
> CANX10hDqudKB9KuF=FMjDs7+SUmTN9F0e7Wz-uwAwuvV+4UszQ at mail.gmail.com
> 

> Content-Type: text/plain; charset="UTF-8"
> 

> On Sun, 19 Jun 2022 at 12:08, Peter West pbw at pbw.id.au wrote:
> 

> > If you wait for 4217, you?ll be waiting a long time.
> > 

> > Or so it seems to me.
> > 

> > ?
> > Peter West
> > pbw at pbw.id.au
> 

> 

> 

> According to the ISO website, they are looking at crypto, but it will not
> be part of ISO 4217. That was written 2.5 years ago ???
> 

> https://www.iso.org/news/ref2466.html
> 

> 

> 

> Dave
> 

> 

> --
> Dr. David Kirkby,
> Kirkby Microwave Ltd,
> drkirkby at kirkbymicrowave.co.uk
> https://www.kirkbymicrowave.co.uk/
> Telephone 01621-680100./ +44 1621 680100
> 

> Registered in England & Wales, company number 08914892.
> Registered office:
> Stokes Hall Lodge, Burnham Rd, Althorne, Chelmsford, Essex, CM3 6DT, United
> Kingdom
> 

> 


> ------------------------------
> 

> Message: 5
> Date: Sun, 19 Jun 2022 11:19:49 -0400
> From: Michael or Penny Novack stepbystepfarm at comcast.net
> 

> To: "Dr. David Kirkby" drkirkby at kirkbymicrowave.co.uk
> 

> Cc: gnucash-user at gnucash.org
> Subject: Re: [GNC] Bitcoin Lightning payments
> Message-ID: 5d7e263c-424a-28a6-3aaf-b12ec86f141c at comcast.net
> 

> Content-Type: text/plain; charset=UTF-8; format=flowed
> 

> > Obviously BTC
> > 

> > In general I think standards are good - especially internationally
> > agreed ones. But according to the ISO website
> > 

> > https://www.iso.org/news/ref2466.html
> > 

> > ISO 4217 is never going to cover cryptocurrencies.? ISO are apparently
> > looking at crypto.
> 

> No, I thought I explained why it COULDN'T be "BTC"
> 

> That choice would violate an existing ISO standard. Unless Bhutan
> adopted Bitcoin as a currency << hey, it might be easier/quicker to get
> Bhutan to do that then getting the ISO to agree. >> The first thing the
> 

> ISO would need to do is settle on what first two characters would be "no
> state". There are lots cryptocurrencies so maybe want several character
> pairs for "no state"
> 

> Michael D Novack
> 


This might speed Bitcoin through ISO, IF actually happens at BIS first:
https://finbold.com/bank-for-international-settlements-to-allow-banks-to-keep-1-of-reserves-in-bitcoin/

ISO is hardly a real NGO; doubtful that they would ever approve a code that central bankers don't.

Keeping a separate Bitcoin book, where 1$ is assumed to be 1 sat is workable so far, including for milisat accounting.
How to link it to our fiat ledger is the next question.

Should it be done by using GC as an sql file and setting up some database connector between the fiat and the Bitcoin files?

HSC
  
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 249 bytes
Desc: OpenPGP digital signature
URL: <http://lists.gnucash.org/pipermail/gnucash-user/attachments/20220701/d8aad52f/attachment.sig>