BNSWG Meeting Notes

larry · November 5, 2021, 9:26am

Notes from BNS Working group meetings are available on github and will be posted in this thread.

larry · November 5, 2021, 9:26am

BNSWG 2021-10-07 1300-1330 UTC

Attendees: Marvin, Mark, Thomas, Larry

Summary

There is general interest in improving BNS so that it can be more widely used in the ecosystem and enable new business models. We want to involve in more stakeholders.

Agenda

Intro: How you plan to use BNS, your interest in this working group
BNS’s position in the stacks ecosystem: traditionally it has been part of the blockchain. Should this continue or should it be separate project built on top of it?
When/How should we engage more community members?
1. Should this be done via the Stacks foundation or separate org?
Ideas for near-term improvements to BNS
1. Reverting previous hard fork changes to BNS:
  1. Solving issue 37 (1 principal can own multiple names) for Stacks 2.1
  2. paying namespace creators instead of burning funds
2. Updating BNS to support SIP-009 NFT Standard
3. Marvin’s BNSv3
Other business

Action items

mark will reach out to additional interested parties
marvin will look at the next steps we need to take with the foundation

larry · November 5, 2021, 9:27am

BNSWG 2021-10-14 1400-1430 UTC

Attendees: Gina, Larry, Mark, Thomas

Summary

We discussed next steps and came up with a list of action items.

Action items

larry will post forum post after call posted
larry will reach out to aaron about multiple names per address
thomas will reach out to ludo about his thoughts
gina will ask btc.us team to write up the problems they had with 1 name per address limitation
larry ping marvin about written version of BNSv3 ideas
larry will ask ken if he’s interested in joining

larry · November 5, 2021, 9:27am

BNSWG 2021-11-04 1400-1430 UTC

Attendees: Gina, Larry, Thomas, Mark, Ken, Alex Gaebe, Eshwari, Ludo, Kyran

Summary

Given the large number of new people on the call, each person explained why they are interested in BNS and the creation of a BNS working group.

We discussed a few of the potential improvements, the creation of a roadmap for BNS and the benefits and drawbacks of tying BNS tightly to the Stacks node software and upgrade process.

We quickly ran out of time and a suggestion was made that we outline the issues and discuss in writing and come back on a longer call in the future to discuss solutions. This was agreed and Larry and Mark volunteered to take the lead on logistics.

Action items

Larry and Mark will work out logistics on 2021-11-05.

larry · November 5, 2021, 2:18pm

BNSWG 2021-11-05 1330-1430 UTC

Attendees: Mark, Larry

Summary

In order to encourage contribution, each person in the BNSWG needs to own an initiative. These initiatives will be tracked and discussed on Github.

Members will be responsible for promoting/selling their initiatives to the wider community through content they produce.

We’ll plan to have at least one monthly recurring call, the appropriate length of which will be determined in the future.

Action items

Mark will write up a README document proposal outlining logistics and how the group will operate.
Larry will create initiatives to kick off discussion around the current potentials initiatives raised by members of the group.

larry · June 2, 2022, 3:36pm

BNSWG 2022-05-05 1400-1500 UTC

Attendees: Mark Hendrickson, Larry Salibra, Louise Ivan, Abdou, Yukan Liao, werner.btc, Hero G

We failed to take notes, but we did create a telegram group for the BNSWG. Available here: Telegram: Join Group Chat

larry · June 2, 2022, 3:36pm

BNSWG 2022-06-02 1400-1500 UTC

Attendees: Larry Salibra, Phillip, Yukan Liao, Werner, Hero G, Marvin Janssen

Agenda

Upgrade path for BNS
Creation of a SIP proposal to fix existing bugs
Other business

Upgrade path for BNS

We discussed the options: hark-forking the existing contract with Stacks 2.1 vs deploying a new contract and getting other people to use it. As a lot of things are hardcoded to the current contract address, the general consensus seemed to be hardforking was the better method.

Proposing a SIP to fix problems with existing BNS contract

Larry proposed these items to be included in a proposed:

name-renewal should burn fees BNS: Name renewal does not burn STX tokens · Issue #2973 · stacks-network/stacks-blockchain · GitHub
name-renewal should transfer name to new owner (it appears not to do this now - Mark mentioned this is a known issue but I haven’t verified it myself)
multiple names per account
conform to SIP-0009 NFT standard

Discussion:

Multiple names per contract is allowed already if you include subdomains
One participant is launching a service that gives the subdomain on bns to the owner of the same ICANN subdomain
Pricing of namespaces is too rigid: it prevents use cases like Chile’s NIC buying .cl and selling names with their ICANN names.
Why don’t we have a voting contract for BNS? We have this for stacks. (Discussed in relationship to the inflexibility of name/namespace pricing)
The intent of proposing these bug fixes / non-controversial changes is to start a discussion about what we want for BNS in the future.

Other business

Xverse wants to make it so that you can send bitcoin to a BNS name.

Discussed proposing a SIP vs unilaterally coming up with their own format.
We talked about how hypothetically in the future it might make sense for standards that only relate to BNS to go through BNSIP process separate from the SIP process.
Larry mentioned that we previously had support for adding a bitcoin (or other addresses) to profiles. This is from larry.id’s profile and how it was previously done:

{
  "identifier": "1EyuZ8qxdhHjcnTChwQLyQaN3cmdK55DkH",
  "role": "payment",
  "@type": "Account",
  "service": "bitcoin",
  "placeholder": false
}

Discussed about using BNS via bitcoin.

Prior to Stacks 2.0 you could registered some names with only BTC
We agree that BNS should be more tightly tied to bitcoin
We liked the idea of making BNS the best name system it can be for bitcoin.
It’s unclear if we still register .ids with only bitcoin
Discussed the possibility of two approaches to tying BNS more closely to bitcoin
1. Making it so that certain namespaces require you to send/burn some BTC to register a name in that namespace
2. Make it possible to register names only through bitcoin without having to interact with stacks nodes at all - using something similar to the Stacks 1.0 OP_RETURN format. These names would exist in stacks nodes as well. It’s unclear if stacks would be able to read them with current functionality today

Action items:

Separate controversial items in a separate SIP: multiple names per account was the only controversial item we found
ask Friedger:
- if he’s encountered any other bugs in the BNS smart contract
- using BNS with bitcoin, ask about SIP process
ask Jude about ability to register .id names with bitcoin

larry · May 24, 2023, 1:55pm

Meeting notes from 2023-05-11’s meeting are here:

github.com

bnswg/meetings/blob/main/2023-05-11.md

# BNSWG 2023-05-11 1430-1530 UTC

Attendees: See video

## Agenda

- Discuss timeline for BNS 2.0 hard fork
- Discuss contentious issues

## Video

https://www.youtube.com/watch?v=CgqTtAXYzRo

## Points discussed

- How to implement the upgrade: should the 2.0 contract be upgradable? If so, how are those upgrade decisions made?
- Multiple names per account: Is the account that owns the name the identity the name refers to or is it the value the name points at?
- How to fund this project going forward: DAO? collect registration fees instead of burning?
- Name pricing: should we change the core price of .btc? Can we enable pricing of names in different currencies? ie. sBTC

A video recording is here: BNS Working Group Meeting - 2023-05-11 - YouTube

Note that I edited out the zoom bombers that screen shared NSFW content during the meeting.

As always, older notes are in the BNS WG github repo here: GitHub - bnswg/meetings

larry · July 20, 2023, 4:15pm

Videos and transcripts for the past 4 meetings are available on the Youtube channel / in the Github repo:

github.com

bnswg/meetings/blob/main/2023-06-08.md

# **BNS Working Group public meeting (2023-06-08 22:37 GMT+8) - Transcript**

## **Video**

https://youtu.be/pYC2uIorHxw

## **Attendees**

3 id, Cordy Joseph, Deloon M, Don Ruiz, Gina Abrams, Hank Stoever, Jeff Domke, Larry Salibra, Tommy Butcher

## **Transcript**

_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._

Hank Stoever: Could be normalizing everything to five years, you know. And then the same thing on pricing and so it's like, What do you do for new registrations? What do you do for existing registrations? You know how exactly does that go about and then and then we can sort of, you know, figure out. Whether or if we move forward with that,

3 id: Yeah, I'm happy to put sort of a template together into stickler on the Forum.

Hank Stoever: Okay. Great.

This file has been truncated. show original

github.com

bnswg/meetings/blob/main/2023-06-22.md

# **BNS Working Group public meeting (2023-06-22 22:34 GMT+8) - Transcript**

## **Video**

https://youtu.be/IofeJ3s1WHU

## **Attendees**

3 id, Cordy Joseph, Deloon M, Gina Abrams, Larry Salibra, Snazzy, Tommy Butcher

## **Transcript**

_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._

Tommy Butcher: Looks that way.

Larry Salibra: No everybody. Welcome to at this last edition for 2023 of The Bns Working Group. Yeah, I don't.

Snazzy: Blue.

This file has been truncated. show original

github.com

bnswg/meetings/blob/main/2023-07-06.md

# **BNS Working Group public meeting (2023-07-06 22:32 GMT+8) - Transcript**

## **Video**

https://youtu.be/I5r2eQwdFOw

## **Attendees**

Deloon M, Don Ruiz, Gina Abrams, Hank Stoever, Jeff Domke, Larry Salibra, Mark Hendrickson, Ragnar Lifthrasir

## **Transcript**

_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._

Larry Salibra: Okay, recording has started. Welcome everybody. I think.

Larry Salibra: so last week I think no one here was here. Except for maybe Gina briefly and I don't know if you able to check out the video. It was basically end up being a conversation or even two weeks ago in me and a number of members of the Bns Dow Council. And so they communicated their desire for sort of a group that works in this whole time funding and sort of basically it was discussion around this. And then since then there's been some calls outside of this about creating an organization. I think custom machine has been taking the lead in that.

Larry Salibra: perhaps, so that's one thing that's gonna be able. I was not table is Hank, was working on an app to collect feedback from the community with regard to which being Bns 2.0. And I think, a third thing is a discussion of making Bns interoperable, layer one, and a way that makes sense for the market. So I suggest we discuss one of those three things.

This file has been truncated. show original

github.com

bnswg/meetings/blob/main/2023-07-20.md

# **BNS Working Group public meeting (2023-07-20 22:32 GMT+8) - Transcript**

## **Video**

https://youtu.be/CuV5Twz2kQo

## **Attendees**

3 id, Deloon M, Don Ruiz, Gina Abrams, Larry Salibra, Mark Hendrickson, Patrick Stanley, Pedro Reis Colaço, Ragnar Lifthrasir, Tommy Butcher

## **Transcript**

_This editable transcript was computer generated and might contain errors. People can also change the text after it was created._

Larry Salibra: Okay, so welcome I think today is a good opportunity to take some time to discuss some of the issues around. Thanks for imposts about Bns names and L1 there's been a lot of really good discussion on the Forum and sometimes it helps to have a bit more discussion vocally in real time and then maybe we can use that time for this. What is everybody think?

3 id: Yep, sounds great.

Larry Salibra: Okay, I'm going to share a link to that just in case what I'm talking about.

This file has been truncated. show original