From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on gnuweeb.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=ALL_TRUSTED,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,NO_DNS_FOR_FROM,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.6 Received: from mail-lf1-f43.google.com (mail-lf1-f43.google.com [209.85.167.43]) by gnuweeb.org (Postfix) with ESMTPSA id 571787E718 for ; Wed, 15 Jun 2022 10:00:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=gnuweeb.org; s=default; t=1655287219; bh=knR+LCy58NKeIaRJlatKZ4ki+v5nZyXjA0BQ1lH0V4M=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=MfhGbBpvwNjFIMASiHD9kU+eD/1XQZrbQCHnANl4xkkOD9PJ7RRZgznMJOi2qfCl0 U7dWlY+x6LjgqGSp/ekVquW41VvTKoMZMgCyZQzxnlqG8gpfvuAROWVQVqWVBg+Vxd wfa4h0WMGXN/4fRnbhq3F3q+qZ+QYnkodFNJ47Nw2/GANGzzAfUX3ReJhFfl5G+DVJ 2RJNJv9h6Vm+3ciazpl5FRkDuS0LnDnnD3aBrAlrnEXAb+0EP1kNm7mKgM1zdb0lFJ fUWTTY4CT8jEAQlM8B+0EkhpqlwNpk6RSfVb8itbtvElV7f/0mJdxiw3vKqLZ/QTLg xnEJKdljpT4ag== Received: by mail-lf1-f43.google.com with SMTP id 20so18058091lfz.8 for ; Wed, 15 Jun 2022 03:00:19 -0700 (PDT) X-Gm-Message-State: AJIora8FZnL2nv2QbVJWCvqEByYC5vyYRqkYzSGlOMI8V9cqH+xZZwL5 7OK92YrqyxKh3+vDk+Uo74FyiqEF8XoD5LVAByo= X-Google-Smtp-Source: AGRyM1sBU4z4mNfqyYzwwOmRJi3DvGopLa3YPOdKqd/0dhgkx0TOWCT6xmfrPaZrPnIyPnNq+XEnkURUPeljBY/egCs= X-Received: by 2002:ac2:55ae:0:b0:479:606:a3e9 with SMTP id y14-20020ac255ae000000b004790606a3e9mr5627669lfg.146.1655287217501; Wed, 15 Jun 2022 03:00:17 -0700 (PDT) MIME-Version: 1.0 References: <1dc7ad7c-914a-001c-1d7c-fc8433e9b609@gnuweeb.org> In-Reply-To: <1dc7ad7c-914a-001c-1d7c-fc8433e9b609@gnuweeb.org> From: Alviro Iskandar Setiawan Date: Wed, 15 Jun 2022 17:00:05 +0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC] GNU/Weeb Financial Transaction Record Design To: Ammar Faizi Cc: "GNU/Weeb Mailing List" Content-Type: text/plain; charset="UTF-8" List-Id: On Wed, Jun 15, 2022 at 4:42 PM Ammar Faizi wrote: > Several questions below: > > 1) What are the exact fields we are going to save? I will post the DDL with exact fields we are going to save to answer this question. > 2) How do we maintain a new field in the future if we ever add more? Maybe just make them be an empty string. Appending an empty string won't change the hash because it doesn't change anything. For example, we create a new field x, make it nullable, if it's NULL then when we're validating the old records that don't have this field just treat it as an empty string, it won't change the hash, so it's backward compatible. > 3) How do we distribute the trusted chains to public? > > For no (2), you must not break the old records that don't have the new > field. > > For no (3), I think it's quite simple, just post the transaction > history record periodically to the group. We can use a Telegram bot > for that. I agree with you. > [ Anyway, you can start writing the code. ] oc tq -- Viro