From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Fri, 11 Jul 2025 11:48:24 -0700 Received: from mail-oo1-f62.google.com ([209.85.161.62]) by mail.fairlystable.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1uaInH-0007Wo-NI for bitcoindev@gnusha.org; Fri, 11 Jul 2025 11:48:24 -0700 Received: by mail-oo1-f62.google.com with SMTP id 006d021491bc7-610bf6f2c8bsf2334004eaf.3 for ; Fri, 11 Jul 2025 11:48:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20230601; t=1752259697; x=1752864497; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:sender:from:to:cc:subject:date :message-id:reply-to; bh=gDY6l8VXZiq1DvTJ/1QqFb55QQ41vjKEXVzKOfUtMaU=; b=VXrxonx7bi/2UTSmKzA+tofvSVxE5PpVbQBFyb85HMdVzgo95NEKzaY5q/0xUNoylf J0vgMXbmCBkjMVS4MJgQmnjyCCV+ucV7XMCueLCS0NJhM08gjAZeb3wu4IRL4H1V9qAc y4uo8rhZUDswoT5Jq/6L349ee2Vc8K4jHXH1XLcacGNtsJF1GlxbpDq1tsl6moh1mQ1a KDgWimalSlt0c5tl7kILpANu8I5ekracVzIIQWI1rfPBI+SzA7sY/nS4VZ7FVdvCmJZP sm743UUON1uYg2TBu3UwgOGisetcE8XNAF5Zq9Vhf0z/om5DeWdcWlwRoK3l0DSpD+uF 7SbQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1752259697; x=1752864497; darn=gnusha.org; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:from:to:cc:subject:date:message-id :reply-to; bh=gDY6l8VXZiq1DvTJ/1QqFb55QQ41vjKEXVzKOfUtMaU=; b=d+9F9NCnZTURjjCHMi/ww6rK5reKReNTKJHY39YHNpKfWSwET2C5M8T8CvW9LNXZwf aLMd+56DER1IDkYhAjFSTYx6Us2d4xiWxsw/Pp6hqT3DfIKPhuR264b3Y8GwU3jFXnQR V96pEnc7BOlRjxYOxZJ/9Lt85XLBJ/nlWjNuu/QhPFEaPcjPCHY7L7+FhTmiEDy2nFQ8 nMqaLCp7sRliFDarpiyCm8QPjmsflaJVNz1LqGqXtkvoq7h/VAreFe+nONaTb1NrMkYo zy6k9DT1XeV4YAKvszBPOqWlC3yYo72MfX/uO2QOg017YS29SxcFNMDJBws78FZ8yZfV MLpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1752259697; x=1752864497; h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post :list-id:mailing-list:precedence:x-original-sender:mime-version :subject:message-id:to:from:date:x-beenthere:x-gm-message-state :sender:from:to:cc:subject:date:message-id:reply-to; bh=gDY6l8VXZiq1DvTJ/1QqFb55QQ41vjKEXVzKOfUtMaU=; b=gQ7CF0D4OqDb57OeNvoL991G+HhPON3tuAjavbIH1LVQ2ybvGQYGp0t3Im9iG39P6r YJmqnqMGSIhpr1GkTjiK8AlFjVCTXhAS8QWTZjsxK0N3rawGN3y90oSEO1IQ1ph3FJWU TZoGa9bqDXi2UCFdCybB6amc42n+GIlr7V4gFmMHr0t+VjChKCzuj5d+i6BfqqCgfI9g 5twP1zJdTl7JhK8OmMyEqRSFpPfo5Htvb6lmk0ZYzV30bwI7eI01UmKx6QLuKT8udj2V sRVPhuNzamwoo6CI/aGFBvkw/AqcAYZRvrDQP1tPO3v08cV80oKBsKxi60ynMWZXXi3I QKDQ== Sender: bitcoindev@googlegroups.com X-Forwarded-Encrypted: i=1; AJvYcCVgiL4tL2iQqVFSsyE+OSJl5TslZKKJR92bKv3unUmSnS7+QV8Iwwu4mI/a2nt4LApvusfP+Z+AFriL@gnusha.org X-Gm-Message-State: AOJu0YxDarbhjbP/KCU5aJ3xIU5CZm5HeI/We5LRcKXTFFLS+l5j7eJI mbvJ6+RRmHwvE9+Zkmnh3AG6A1EXMUkAZWEymPAKMkfsyXjF94+kz7i9 X-Google-Smtp-Source: AGHT+IF05Ibv6cpbnslDl4GZo//Q3Jr9TroR9NTb+eNYtMMkowBOnlAoZ4cCvhWDBTPdC3GikmvTYQ== X-Received: by 2002:a05:6820:211:b0:611:a1e4:59ad with SMTP id 006d021491bc7-613e7aea783mr2423053eaf.4.1752259697211; Fri, 11 Jul 2025 11:48:17 -0700 (PDT) X-BeenThere: bitcoindev@googlegroups.com; h=AZMbMZdeRqUWfGDtSBdk1Hl5KchCnRpBuziHJxGPZCOddtZltQ== Received: by 2002:a05:6820:610b:b0:611:950c:4b25 with SMTP id 006d021491bc7-613d7ce9e65ls445253eaf.2.-pod-prod-08-us; Fri, 11 Jul 2025 11:48:13 -0700 (PDT) X-Received: by 2002:a05:6808:3998:b0:40c:fcbd:61a4 with SMTP id 5614622812f47-41537277e36mr2810199b6e.2.1752259693639; Fri, 11 Jul 2025 11:48:13 -0700 (PDT) Received: by 2002:a05:690c:d8b:b0:710:f35d:a3b2 with SMTP id 00721157ae682-7166a91b6ffms7b3; Fri, 11 Jul 2025 07:25:48 -0700 (PDT) X-Received: by 2002:a05:690c:4a10:b0:70c:c013:f26 with SMTP id 00721157ae682-717d7a668d6mr49998837b3.33.1752243946283; Fri, 11 Jul 2025 07:25:46 -0700 (PDT) Date: Fri, 11 Jul 2025 07:25:45 -0700 (PDT) From: Maxim Orlovsky To: Bitcoin Development Mailing List Message-Id: <90cb419b-93e9-4fab-8ce2-5e016932ab8fn@googlegroups.com> Subject: [bitcoindev] RGB consensus layer released for production deployments MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_Part_104066_100154338.1752243945899" X-Original-Sender: dr.orlovsky@gmail.com Precedence: list Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com List-ID: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , X-Spam-Score: -0.5 (/) ------=_Part_104066_100154338.1752243945899 Content-Type: multipart/alternative; boundary="----=_Part_104067_457472598.1752243945900" ------=_Part_104067_457472598.1752243945900 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello all, I am glad to inform that after years of development (6 years since I had=20 joined to lead the project, and about 8-9 years in total) RGB finally got= =20 stable: yesterday its consensus was released as RGB-I-0 (provided by=20 `rgb-core` rust crate of v0.12; more on version numbering can be found in= =20 https://github.com/RGB-WG/RFC/blob/master/RGB-6.md). In client-side validation world we face more complex change rules than in= =20 bitcoin blockchain: if something was valid before and becomes invalid=20 (soft-fork in blockchain), in the client-side validation this is becomes a= =20 backward-incompatible change (functionally similar to a hard-fork). Thus,= =20 release of consensus layer for RGB had required us to build its complete=20 functionality, which is kind of ossified from the day of the release, with= =20 a very small surface for possible future changes or upgrades. Anyway, here we are: finally the protocol is complete, with all required=20 functionality (including support for zk-STARK compression) being present=20 there. Adding zk-STARK support was quite a challenge, which took most of=20 the last year, and required to re-think and re-do the virtual machine and= =20 the full computing environment which was used by RGB. You can read the full= =20 information about what=E2=80=99s coming with the released consensus layer i= n the=20 official release=20 announcement: https://rgb.tech/blog/release-v0-12-consensus/ Those who are interested about more details what RGB is, may also watch my= =20 presentation at the past BTC Pragure RGB=20 side-event: https://www.youtube.com/watch?v=3DQ34QcP2GMMU NB: This is a consensus layer release, with standard library and=20 application-level library releases to follow during the next weeks.=20 However, this release is the most important among all of them, since it is= =20 only consensus changes which can break contracts backward compatibility,=20 while the changes to any layers on top may require software or wallet=20 updates =E2=80=93 but would never break contracts and assets which were alr= eady=20 issued. Thus, with this release, contracts become forward-compatible. Developers and issuers can now deploy contracts on testnet and Bitcoin=20 mainnet using this stable release. But for security and consistency, please= =20 re-issue any contracts created with pre-release versions. Kind regards, Maxim Orlovsky Lead engineer at LNP/BP Standards Association & Pandora Prime SA --=20 You received this message because you are subscribed to the Google Groups "= Bitcoin Development Mailing List" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoindev+unsubscribe@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/= 90cb419b-93e9-4fab-8ce2-5e016932ab8fn%40googlegroups.com. ------=_Part_104067_457472598.1752243945900 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hello all,

I am glad to inform that after years of dev= elopment (6 years since I had joined to lead the project, and about 8-9 yea= rs in total) RGB finally got stable: yesterday its consensus was released a= s RGB-I-0 (provided by `rgb-core` rust crate of v0.12; more on version numb= ering can be found in https://github.com/RGB-WG/RFC/blob/master/RGB-6.md).<= /div>

In client-side validation world we face more com= plex change rules than in bitcoin blockchain: if something was valid before= and becomes invalid (soft-fork in blockchain), in the client-side validati= on this is becomes a backward-incompatible change (functionally similar to = a hard-fork). Thus, release of consensus layer for RGB had required us to b= uild its complete functionality, which is kind of ossified from the day of = the release, with a very small surface for possible future changes or upgra= des.

Anyway, here we are: finally the protocol i= s complete, with all required functionality (including support for zk-STARK= compression) being present there. Adding zk-STARK support was quite a chal= lenge, which took most of the last year, and required to re-think and re-do= the virtual machine and the full computing environment which was used by R= GB.=C2=A0You can read the full information about what=E2=80=99s comin= g with the released consensus layer in the official release announcement:= =C2=A0https://rgb.tech/blog/release-v0-12-consensus/

Those who are interested about more details what RGB is, may al= so watch my presentation at the past BTC Pragure RGB side-event:=C2=A0https= ://www.youtube.com/watch?v=3DQ34QcP2GMMU

NB: This is a consensus layer release, with standard library and application= -level library releases to follow during the next weeks. However, this rele= ase is the most important among all of them, since it is only consensus cha= nges which can break contracts backward compatibility, while the changes to= any layers on top may require software or wallet updates =E2=80=93 but wou= ld never break contracts and assets which were already issued. Thus, with t= his release, contracts become forward-compatible.

Developers and issuers can now deploy contracts on testnet and Bit= coin mainnet using this stable release. But for security and consistency, p= lease re-issue any contracts created with pre-release versions.
=

Kind regards,
Maxim Orlovsky
Lead= engineer at
LNP/BP Standards Association
& Pandora= Prime SA

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoind= ev/90cb419b-93e9-4fab-8ce2-5e016932ab8fn%40googlegroups.com.
------=_Part_104067_457472598.1752243945900-- ------=_Part_104066_100154338.1752243945899--