WEBVTT 00:00:05.320 --> 00:00:12.259 Howdy everyone, Sandow Podcast. This is Sandow69, 00:00:12.859 --> 00:00:17.339 and we're doing a SIP review of SIP39, pausing 00:00:17.339 --> 00:00:23.120 the Sandbox DAO. Today is a non -discussion, 00:00:23.300 --> 00:00:26.359 a read -through, and a little bit of commentary. 00:00:28.480 --> 00:00:30.820 Disclaimer, I do not represent the Sandbox game 00:00:30.820 --> 00:00:33.460 or the Sandbox Foundation. I'm not your financial 00:00:33.460 --> 00:00:35.560 or legal advisor. Nothing I say is to be taken 00:00:35.560 --> 00:00:37.960 as financial or legal advice. When I say the 00:00:37.960 --> 00:00:40.420 word SIP, I mean Sandbox Improvement Proposal. 00:00:40.679 --> 00:00:43.039 When I say the word DAO, I mean Decentralized 00:00:43.039 --> 00:00:46.159 Autonomous Organization. If I use the word SanFam, 00:00:46.179 --> 00:00:48.060 I'm talking about the Sandbox community, those 00:00:48.060 --> 00:00:50.560 who participate in the people, product, and purpose 00:00:50.560 --> 00:00:53.960 of the Sandbox ecosystem. That ecosystem looks 00:00:53.960 --> 00:00:55.920 a little bit like this, where you have in the 00:00:55.920 --> 00:00:58.399 people side, everything from the gamers of the 00:00:58.399 --> 00:01:00.420 Sandbox team. The product is everything from 00:01:00.420 --> 00:01:03.399 the game client to the DAO itself. Purpose is 00:01:03.399 --> 00:01:06.680 the white paper as expounded upon by Sébastien 00:01:06.680 --> 00:01:12.019 Bourget, Arthur Moudadid, Yat Tzu. And that equals 00:01:12.019 --> 00:01:14.200 the ecosystem, which goes round and round each 00:01:14.200 --> 00:01:19.480 day. And today's episode is on the DAO. If you'd 00:01:19.480 --> 00:01:21.140 like to learn more about the ecosystem and the 00:01:21.140 --> 00:01:24.019 DAO and how it works, go to the DAO Education 00:01:24.019 --> 00:01:29.680 Hub in the Sandbox Metaverse located at 2 -154. 00:01:30.359 --> 00:01:34.000 It is in the bottom left of the map, right next 00:01:34.000 --> 00:01:37.500 to Jurassic World. My name is Lanzer, I'm your 00:01:37.500 --> 00:01:40.739 host, and I run the MetaWorlds group. We've done 00:01:40.739 --> 00:01:45.680 a number of things, a few experiences to include 00:01:45.680 --> 00:01:48.379 floor droppers. Also, we built the DAO Education 00:01:48.379 --> 00:01:56.239 Hub after winning an RFP from a SIP. And landowner, 00:01:56.480 --> 00:02:00.500 avatar holder, I've been part of. sandbox ecosystems 00:02:00.500 --> 00:02:05.180 it's about 2021 like i mentioned today we'll 00:02:05.180 --> 00:02:07.700 be talking about sip 39 we'll be doing a read 00:02:07.700 --> 00:02:11.659 -through of it it traces all the way back to 00:02:11.659 --> 00:02:15.900 august 2025 of last year when big whale gaming 00:02:15.900 --> 00:02:21.060 daily kate irwin and they came out with some 00:02:21.060 --> 00:02:25.860 articles revealing that the sandbox had been 00:02:25.860 --> 00:02:31.199 realigned and that it that a new CEO came in 00:02:31.199 --> 00:02:34.000 from Animoca Brands, Robbie Young, stepped in 00:02:34.000 --> 00:02:38.280 in order to synergize a new way forward for the 00:02:38.280 --> 00:02:43.159 Sandbox, which through time we learned was Sandbox 00:02:43.159 --> 00:02:50.080 3 .0. So through some AMAs that happened the 00:02:50.080 --> 00:02:54.280 past couple months, mostly also the SIP39 AMA 00:02:54.280 --> 00:02:59.699 that happened just a couple weeks ago. I did 00:02:59.699 --> 00:03:03.900 a couple of my last two episodes, Sandow 67 and 00:03:03.900 --> 00:03:09.919 Sandow 68. 67 was a commentary on the AMAs themselves, 00:03:10.020 --> 00:03:12.860 and 68 was an interview of Sebastian Bourget, 00:03:12.919 --> 00:03:15.819 who is now the global brand ambassador for the 00:03:15.819 --> 00:03:19.520 Sandbox, still the co -founder. So that was part 00:03:19.520 --> 00:03:23.060 two of an interview that we started back in Sandow 00:03:23.060 --> 00:03:26.219 8. We learned a lot about the new way forward 00:03:26.219 --> 00:03:29.479 from both of those episodes. And now is a read 00:03:29.479 --> 00:03:35.139 -through of SIP39, as it is now live on Snapshot. 00:03:36.500 --> 00:03:38.000 So that's what we're going to do here today, 00:03:38.199 --> 00:03:40.539 is read through it. A little bit of commentary, 00:03:40.659 --> 00:03:42.879 but most of my commentary was done in Sandow67. 00:03:43.740 --> 00:03:46.580 And questions and answers and follow -up were 00:03:46.580 --> 00:03:50.259 Sandow68 with Sebastian Bourget. So, without 00:03:50.259 --> 00:03:59.960 further ado, let's start. SIP39, Pausing the 00:03:59.960 --> 00:04:03.900 Sandbox DAO, was put out by Arasakyo, which is 00:04:03.900 --> 00:04:09.439 the DAO administrator company headed up by Cyril. 00:04:09.599 --> 00:04:12.900 We interviewed him not long ago. I think it was 00:04:12.900 --> 00:04:21.439 a few months ago. Sandow61 -ish. It went live 00:04:21.439 --> 00:04:30.250 today. So the TLDR. The what? SIP 39 pauses the 00:04:30.250 --> 00:04:33.689 Sandbox DAO. No new SIP intake, no new funding 00:04:33.689 --> 00:04:36.730 decisions, and a shift to minimum maintenance 00:04:36.730 --> 00:04:39.170 mode to preserve assets and remain compliant. 00:04:41.910 --> 00:04:45.810 The why? The Sandbox is entering a new phase 00:04:45.810 --> 00:04:48.269 with the Sandbox 3 .0, and this pause creates 00:04:48.269 --> 00:04:51.189 space to reassess the DAO's purpose and operating 00:04:51.189 --> 00:04:55.740 model before taking on any new commitments. And 00:04:55.740 --> 00:04:57.540 I'll be taking notes here so I can go back to 00:04:57.540 --> 00:05:02.120 it at the very end. The how. The pause is implemented 00:05:02.120 --> 00:05:05.480 via a formal SIP and vote. Responsibilities for 00:05:05.480 --> 00:05:08.240 finance, assets, and contracts transition to 00:05:08.240 --> 00:05:11.360 this inbox team. Active SIPs continue through 00:05:11.360 --> 00:05:13.879 the end of quarter one, 2026, where applicable. 00:05:14.639 --> 00:05:19.660 SIP 26, SIP 33, and SIP 36 are terminated, canceled. 00:05:21.740 --> 00:05:25.209 And now we get into the when. Effective date 00:05:25.209 --> 00:05:30.329 is 25th of February, 2026, which is about when 00:05:30.329 --> 00:05:33.949 they estimate the SIP 39 is going to pass. So 00:05:33.949 --> 00:05:35.649 you can see down here in the bottom right, it 00:05:35.649 --> 00:05:42.110 is the exact day that the SIP would pass if voted 00:05:42.110 --> 00:05:47.769 yes. Transition period until 31 March, 2026. 00:05:48.050 --> 00:05:55.560 Dormant mode from 1 April, 2026. Who? The Sandbox 00:05:55.560 --> 00:05:57.000 in coordination with the Sandbox Foundation, 00:05:57.259 --> 00:05:59.459 implemented by the Sandbox and the Sandbox Foundation, 00:05:59.819 --> 00:06:02.240 with support from the DAO administrator through 00:06:02.240 --> 00:06:09.199 March 2026. Now we get into the SIP detail section. 00:06:09.579 --> 00:06:12.459 Problem description. Since its inauguration in 00:06:12.459 --> 00:06:17.160 May 2024, the Sandbox DAO has built a community 00:06:17.160 --> 00:06:19.279 of thousands of members, authors, and voters 00:06:19.279 --> 00:06:22.819 from more than 20 countries. to allocate sand 00:06:22.819 --> 00:06:26.000 in support of the sandbox ecosystem, distributed 00:06:26.000 --> 00:06:30.379 more than 3 million sand across 38 SIPs, generated 00:06:30.379 --> 00:06:36.459 8 ,000 forum posts and 500 threads, experimented 00:06:36.459 --> 00:06:39.360 with community governance and decentralized decision 00:06:39.360 --> 00:06:42.860 -making. They're referring to the Sandbox DAO 00:06:42.860 --> 00:06:48.100 Grants Program, the SDGP. However, over that 00:06:48.100 --> 00:06:49.800 same period, we have identified the following 00:06:49.800 --> 00:06:52.699 challenges. The sandbox ecosystem is rapidly 00:06:52.699 --> 00:06:54.839 evolving and the types of initiatives supported 00:06:54.839 --> 00:06:57.199 by the DAO is not clearly aligned with those 00:06:57.199 --> 00:07:02.100 changes. With operating costs invoiced in USD 00:07:02.100 --> 00:07:06.459 euros, the decline in sand price means the DAO 00:07:06.459 --> 00:07:08.699 must self -spend more sand to cover the same 00:07:08.699 --> 00:07:11.800 fixed cost, making the current operating model 00:07:11.800 --> 00:07:14.579 materially more expensive. Continuing operations 00:07:14.579 --> 00:07:17.439 without an updated mandate risks further misalignment 00:07:17.439 --> 00:07:20.839 and value leakage. Pausing creates space to reassess 00:07:20.839 --> 00:07:22.740 how the DAO can best serve the community and 00:07:22.740 --> 00:07:27.000 ecosystem. Solution proposed. For the purpose 00:07:27.000 --> 00:07:31.939 of this SIP, pause the DAO means 1. No new funding 00:07:31.939 --> 00:07:35.100 SIPs. No new grant SIPs or budget SIPs will be 00:07:35.100 --> 00:07:41.199 accepted, curated, or put to vote. 2. Existing 00:07:41.199 --> 00:07:44.480 SIPs. SIPs with signed contracts and or remain 00:07:44.480 --> 00:07:47.579 obligations will be either executed to completion 00:07:47.579 --> 00:07:50.420 or terminated in accordance with the relevant 00:07:50.420 --> 00:07:53.879 contract terms where a contract exists, such 00:07:53.879 --> 00:07:57.939 as notice period or RADA settlement where applicable. 00:07:58.800 --> 00:08:03.959 SIPs without contracts and not yet started will 00:08:03.959 --> 00:08:06.100 be reviewed and closed where applicable during 00:08:06.100 --> 00:08:08.660 the transition period. Authors of the affected 00:08:08.660 --> 00:08:11.060 SIPs will be contacted directly by email during 00:08:11.060 --> 00:08:13.060 the transition period with a clear status outcome. 00:08:13.620 --> 00:08:16.879 Continue through Q1 2026 or terminate cancel. 00:08:17.769 --> 00:08:20.790 And the next operational steps. A consolidated 00:08:20.790 --> 00:08:24.050 status table will document outcomes SIP by SIP. 00:08:25.689 --> 00:08:29.110 Subsection 3. Governance Bodies. No new governance 00:08:29.110 --> 00:08:31.910 initiatives. For example, special counsel, advisory 00:08:31.910 --> 00:08:34.990 board, or delegate. Elections new or new mandates. 00:08:37.850 --> 00:08:39.990 Existing governance bodies will be discontinued 00:08:39.990 --> 00:08:42.389 or moved into a dormant role with no active mandate 00:08:42.389 --> 00:08:45.169 unless explicitly reactivated by a future SIP. 00:08:45.889 --> 00:08:50.190 Transition operations to the Sandbox team. Administrative 00:08:50.190 --> 00:08:52.269 activities will be transferred to the Sandbox 00:08:52.269 --> 00:08:54.830 and reduced to the minimum required to preserve 00:08:54.830 --> 00:08:58.029 the Sandbox Foundation's assets for it to remain 00:08:58.029 --> 00:09:01.190 compliant. As part of this transition, Arasakia 00:09:01.190 --> 00:09:03.149 will progressively hand over operational access 00:09:03.149 --> 00:09:06.610 for finance and asset tooling, including custody 00:09:06.610 --> 00:09:09.549 and banking and payment. Accounting and reporting 00:09:09.549 --> 00:09:11.429 workflows, including sub -ledger replacement 00:09:11.429 --> 00:09:15.360 plans. Governance tools and infrastructure, such 00:09:15.360 --> 00:09:18.639 as snapshot admin, website, forum, DNS, etc. 00:09:19.799 --> 00:09:21.919 Arasakia will no longer act as the DAO administrator 00:09:21.919 --> 00:09:26.360 starting 31 March 2026. Arasakia will support 00:09:26.360 --> 00:09:31.340 the handover through that date. SIP impact. If 00:09:31.340 --> 00:09:34.100 SIP 39 is approved, the following applies. DAO 00:09:34.100 --> 00:09:36.960 activities pause. No new SIP intake, no new programs. 00:09:37.860 --> 00:09:40.220 Existing SIPs are handled per the rules above. 00:09:40.840 --> 00:09:42.840 Continue through quarter 2026 for applicable. 00:09:43.200 --> 00:09:50.360 Terminate, cancel. SIP 26, SIP 33, SIP 36. Responsibilities 00:09:50.360 --> 00:09:52.759 transition to the Sandbox team. AirSakyo provides 00:09:52.759 --> 00:09:57.600 handover support through 31 March 2026. Benefit 00:09:57.600 --> 00:10:00.419 to the Sandbox ecosystem. Time and space to align 00:10:00.419 --> 00:10:03.720 with the Sandbox 3 .0 vision. The Sandbox ecosystem 00:10:03.720 --> 00:10:06.500 is entering a new phase with the Sandbox 3 .0 00:10:06.500 --> 00:10:09.639 and a pause allows the DAO to reassess its purpose. 00:10:10.090 --> 00:10:12.690 structure, and tooling in line of where the platform 00:10:12.690 --> 00:10:15.230 is heading. Thus, any future activity can be 00:10:15.230 --> 00:10:17.909 designed to meaningfully support creators, players, 00:10:18.190 --> 00:10:21.389 builders in the context of the updated product 00:10:21.389 --> 00:10:26.090 vision. Avoidance of rushed or misaligned funding 00:10:26.090 --> 00:10:29.230 decisions. By halting new SIP intake and funding 00:10:29.230 --> 00:10:31.389 decisions, the DAO avoids committing resources 00:10:31.389 --> 00:10:35.009 to initiatives that may no longer fit the evolving 00:10:35.009 --> 00:10:39.440 ecosystem. This reduces the risk of funding projects 00:10:39.440 --> 00:10:42.120 that struggle to deliver impact or become obsolete 00:10:42.120 --> 00:10:45.659 shortly after approval. Responsible wind -down 00:10:45.659 --> 00:10:48.799 of existing commitments. SIP 39 provides a structured 00:10:48.799 --> 00:10:51.100 approach to handling existing SIPs, allowing 00:10:51.100 --> 00:10:54.000 contracted or in -progress initiatives to complete 00:10:54.000 --> 00:10:56.480 where appropriate, while responsibly winding 00:10:56.480 --> 00:10:59.620 down others according to their terms. This avoids 00:10:59.620 --> 00:11:02.600 abrupt disruption while still prioritizing clear 00:11:02.600 --> 00:11:06.399 scope and controlled commitments. Preservation 00:11:06.399 --> 00:11:10.360 of Community Assets and Treasury Value Causing 00:11:10.360 --> 00:11:13.220 SIP intake and DAO operations reduces the DAO's 00:11:13.220 --> 00:11:15.659 operational footprint. By limiting activity to 00:11:15.659 --> 00:11:17.720 only what is required for compliance and asset 00:11:17.720 --> 00:11:20.100 stewardship, more of the DAO's remaining resources 00:11:20.100 --> 00:11:22.940 are preserved for future use rather than consumed 00:11:22.940 --> 00:11:29.360 by ongoing operations. Risk Analysis Risk 1. 00:11:29.779 --> 00:11:35.120 Confusion for the Community Why? DAO pause and 00:11:35.120 --> 00:11:38.539 SIP terminations may be perceived as deprioritization 00:11:38.539 --> 00:11:43.700 or closing the DAO. Mitigation. Communicate scope 00:11:43.700 --> 00:11:46.480 clearly. Publish consolidated SIP status table. 00:11:46.679 --> 00:11:53.940 Run one structured AMA. Risk number two. Contractual 00:11:53.940 --> 00:11:56.960 disputes. Any termination of existing contracts 00:11:56.960 --> 00:12:02.200 can create legal risk. Mitigation. If applicable. 00:12:02.759 --> 00:12:05.799 Follow contract notice terms and document pro 00:12:05.799 --> 00:12:08.539 rata closeout. Direct outreach to affected authors. 00:12:09.500 --> 00:12:12.480 Risk number three. Operational risk during transition. 00:12:12.879 --> 00:12:17.100 Why? Access, custody, banking, accounting, tooling 00:12:17.100 --> 00:12:21.340 changes. Mitigation is a structured handover 00:12:21.340 --> 00:12:25.340 plan through 31 March 2026. Minimal tools retained 00:12:25.340 --> 00:12:29.960 where needed. Risk number four. Fragmented narrative 00:12:29.960 --> 00:12:33.549 across channels. Why? Conflicting statements 00:12:33.549 --> 00:12:40.909 amplify backlash. Mitigation. Single forum thread 00:12:40.909 --> 00:12:43.789 as a source of truth and limited spokespeople. 00:12:44.490 --> 00:12:49.470 Okay, next section is budget requested. $44 ,400 00:12:49.470 --> 00:12:54.549 USD. Costs of maintaining the DAO assets by Sandbox 00:12:54.549 --> 00:12:58.490 team for one year. Expiring 25th February 2027. 00:12:59.159 --> 00:13:02.240 This will be supported by a specific service 00:13:02.240 --> 00:13:05.000 agreement between the foundation and the sandbox. 00:13:06.799 --> 00:13:12.379 Hmm. Implementation plan section. Milestone number 00:13:12.379 --> 00:13:15.980 one. Freeze new SIP intake. How do we measure 00:13:15.980 --> 00:13:18.840 success? No new SIPs accepted. Process after 00:13:18.840 --> 00:13:22.759 SIP 39 passes. Deliverables. Update SIP intake 00:13:22.759 --> 00:13:26.139 guidance and forum notice stating SIP submissions 00:13:26.139 --> 00:13:28.840 are paused. Expected completion date immediately 00:13:28.840 --> 00:13:32.519 after vote concludes. Also in two, publish consolidated 00:13:32.519 --> 00:13:35.799 SIP status view. How do we measure success? Single, 00:13:35.960 --> 00:13:38.220 shared, reference for SIP status, and next steps. 00:13:39.059 --> 00:13:41.539 Deliverables, consolidated SIP status table published 00:13:41.539 --> 00:13:44.759 on forum to include the SIP number, status, contract, 00:13:45.039 --> 00:13:49.299 yes or no, payments, and decision. Expected completion 00:13:49.299 --> 00:13:52.740 date immediately after vote concludes. Also in 00:13:52.740 --> 00:13:56.779 three, terminate SIP 26. 33 and 36, decisions. 00:13:58.779 --> 00:14:02.179 Decisions implemented cleanly and documented 00:14:02.179 --> 00:14:08.360 is the how do we measure success. Deliverables 00:14:08.360 --> 00:14:11.659 are SIP 26 termination notice and closeout plan. 00:14:11.879 --> 00:14:15.659 SIP 33 and SIP 36 close, cancel before start, 00:14:15.879 --> 00:14:23.559 documented. And expect a completion date. by 00:14:23.559 --> 00:14:26.039 february or march 2026 in line with contract 00:14:26.039 --> 00:14:35.539 terms milestone number four operational handover 00:14:35.539 --> 00:14:38.879 to the sandbox how we measure success the sandbox 00:14:38.879 --> 00:14:42.620 has access and can operate deliverables is a 00:14:42.620 --> 00:14:49.720 access transfer completed checklist when expected 00:14:49.720 --> 00:14:56.299 completion date is By 31 March 2026. Milestone 00:14:56.299 --> 00:15:00.399 5. Comms and channel posture. How do we measure 00:15:00.399 --> 00:15:03.320 success? Single source of truth and limited comms 00:15:03.320 --> 00:15:07.799 footprint. Deliverables. Forum post. One structured 00:15:07.799 --> 00:15:11.940 AMA. And final summary of what changes. Does 00:15:11.940 --> 00:15:16.120 not change. Expected completion date is March 00:15:16.120 --> 00:15:23.429 2026. Milestone 6. dormant dow begins how do 00:15:23.429 --> 00:15:26.529 we measure success now operations pause as defined 00:15:26.529 --> 00:15:29.769 in step 39 deliverables is confirmation post 00:15:29.769 --> 00:15:33.129 pause mods active no new sips operations handled 00:15:33.129 --> 00:15:36.990 by the sandbox starting 1 april 2026 expected 00:15:36.990 --> 00:15:41.029 completion date 1 april 2026. all right the next 00:15:41.029 --> 00:15:43.370 section is the team and author background is 00:15:43.370 --> 00:15:45.870 authored by the sandbox in coordination with 00:15:45.870 --> 00:15:49.009 the sandbox foundation Implemented by the Sandbox 00:15:49.009 --> 00:15:51.269 and the Sandbox Foundation with handover support 00:15:51.269 --> 00:15:57.769 from the Dow Administrator. 31 March 2026. Two 00:15:57.769 --> 00:16:00.649 votes registered as of right now. 13 days left. 00:16:01.330 --> 00:16:09.889 And it is currently a no vote with 3 .7 million 00:16:09.889 --> 00:16:15.710 no votes and 188 yes votes. So right now it's 00:16:15.710 --> 00:16:22.009 99 % no. And 0 .01 % yes, although we know that's 00:16:22.009 --> 00:16:24.789 going to change because the sandbox confirmed 00:16:24.789 --> 00:16:26.549 that they will be voting with their wallets, 00:16:26.590 --> 00:16:29.649 and we went over that AMA in our last episode. 00:16:32.330 --> 00:16:34.850 Okay, so there it is. There's the read -through. 00:16:35.289 --> 00:16:38.769 I'm going to... There's a few things that caught 00:16:38.769 --> 00:16:43.009 my eye that I'm going to go over, and then we'll 00:16:43.009 --> 00:16:48.450 conclude. The first thing I noticed was where 00:16:48.450 --> 00:16:51.009 it said a shift to minimum maintenance mode to 00:16:51.009 --> 00:16:53.509 preserve assets and remain compliant. I think 00:16:53.509 --> 00:16:56.710 what they're talking about there is to register 00:16:56.710 --> 00:17:01.870 annually for a sandbox or a foundation company 00:17:01.870 --> 00:17:04.170 in the Grand Cayman Islands. We went over the 00:17:04.170 --> 00:17:06.710 Grand Cayman Islands in depth in our foundation 00:17:06.710 --> 00:17:11.829 company mini series that we concluded with Sandow 00:17:11.829 --> 00:17:15.559 65. We interviewed a director, lawyers, and all 00:17:15.559 --> 00:17:17.680 that sort of stuff. So check that out if you 00:17:17.680 --> 00:17:20.160 want to know a little bit more how Foundation 00:17:20.160 --> 00:17:24.420 Company is run. The next thing that caught my 00:17:24.420 --> 00:17:26.519 eye is when they mentioned reassess the DAO's 00:17:26.519 --> 00:17:28.539 purpose and operating model before taking on 00:17:28.539 --> 00:17:34.599 any new commitments. So as of right now, they 00:17:34.599 --> 00:17:38.140 could restrict new commitments in its current 00:17:38.140 --> 00:17:43.599 form. I went over this in Sandow. where the old 00:17:43.599 --> 00:17:47.259 process was more of a, let's do this one, the 00:17:47.259 --> 00:17:50.299 old process was you submit a SIP, it goes through 00:17:50.299 --> 00:17:53.279 a discussion, and the special counsel will issue 00:17:53.279 --> 00:17:55.180 a recommendation. It was very straightforward. 00:17:55.539 --> 00:17:57.900 There was nothing stopping you from submitting 00:17:57.900 --> 00:18:00.640 a SIP. However, the new process that came about 00:18:00.640 --> 00:18:05.420 in October 2024 increased it from about 150 days 00:18:05.420 --> 00:18:10.700 to 270 days and introduced a kind of gating where 00:18:10.700 --> 00:18:14.509 you, You post your SIP idea to the subforum, 00:18:14.509 --> 00:18:17.250 and you only get to submit an actual SIP for 00:18:17.250 --> 00:18:22.450 voting if you're invited by the DAO admin team 00:18:22.450 --> 00:18:31.650 to the step three. If you're invited in step 00:18:31.650 --> 00:18:39.240 two here, then you get to submit. via the Typeform 00:18:39.240 --> 00:18:41.500 link. And then you go through DAO admin team 00:18:41.500 --> 00:18:43.660 review and comments, you get the recommendation, 00:18:44.039 --> 00:18:47.680 and then it goes to refinement and then public 00:18:47.680 --> 00:18:51.839 discussion and finally voting. So they already 00:18:51.839 --> 00:18:54.980 were able to restrict which commitments they 00:18:54.980 --> 00:18:57.460 take on if they really wanted to. And they were. 00:18:57.599 --> 00:18:59.839 I've been, I think I've authored maybe seven 00:18:59.839 --> 00:19:03.359 or eight SIPs. Two or three of them passed. One 00:19:03.359 --> 00:19:09.569 of them did not pass. So I know firsthand the 00:19:09.569 --> 00:19:11.930 amount of back and forth that goes along with 00:19:11.930 --> 00:19:15.769 the DAO admin team, and they scrutinize it quite 00:19:15.769 --> 00:19:21.390 well. So they apply a lot of keen eye to whether 00:19:21.390 --> 00:19:23.789 or not it's going to help the community or if 00:19:23.789 --> 00:19:26.390 it's in line with the vision of the sandbox. 00:19:26.769 --> 00:19:31.369 So they already strictly control what SIPs go 00:19:31.369 --> 00:19:34.490 to vote. So that's why that one kind of struck 00:19:34.490 --> 00:19:38.740 me as weird. Because their operating model already 00:19:38.740 --> 00:19:41.680 functions in a way where they can restrict taking 00:19:41.680 --> 00:19:47.079 on new commitments. Okay, they mentioned three 00:19:47.079 --> 00:19:51.079 SIPs that were particularly going to be terminated 00:19:51.079 --> 00:19:56.839 or canceled. And I went over that in Sandow 67 00:19:56.839 --> 00:20:03.140 in depth. But let's take a look here at what 00:20:03.140 --> 00:20:08.420 ones they're referring to. So it's SIP 36, which 00:20:08.420 --> 00:20:10.539 is the land estate sale, and I don't understand 00:20:10.539 --> 00:20:13.099 this one. This one was useful to the sandbox 00:20:13.099 --> 00:20:18.299 on the actual game. It wasn't useful to the DAO. 00:20:18.440 --> 00:20:22.420 It was enabled by the DAO to give a highly sought 00:20:22.420 --> 00:20:26.680 -after tool for people to trade and sell estates. 00:20:26.740 --> 00:20:29.480 Right now, you have to use some unsafe methods. 00:20:30.160 --> 00:20:33.019 In order to do that, and in a very, very long, 00:20:33.119 --> 00:20:36.559 cumbersome, over -the -counter method, all of 00:20:36.559 --> 00:20:40.259 the safe methods that used to happen, like escrows, 00:20:40.440 --> 00:20:44.380 they're gone. I know because I tried somewhat 00:20:44.380 --> 00:20:47.480 recently to buy an estate, and it was an extremely 00:20:47.480 --> 00:20:53.660 difficult process to do. So, the only reason 00:20:53.660 --> 00:20:55.420 I got through is because I really wanted an estate. 00:20:56.380 --> 00:20:58.380 But this tool would have made that really simple. 00:20:59.579 --> 00:21:01.400 I could buy it really easily. Because it would 00:21:01.400 --> 00:21:04.640 integrate with the GBM. Which currently handles 00:21:04.640 --> 00:21:08.859 the auctions. For new land releases. In the sandbox. 00:21:09.180 --> 00:21:11.460 So I have no idea. Why they would shut this one 00:21:11.460 --> 00:21:13.500 down. Why would they cancel it. This is useful. 00:21:13.920 --> 00:21:17.960 And built into the sandbox games website. So 00:21:17.960 --> 00:21:22.079 there you go. Civ 33. The sandbox metaverse campus. 00:21:22.519 --> 00:21:24.460 Metaversity campus. Over in the Philippines. 00:21:24.799 --> 00:21:26.859 I guess I can kind of understand that one. Because 00:21:26.859 --> 00:21:31.059 it was more about. bringing attention to the 00:21:31.059 --> 00:21:34.700 sandbox. And if they're pivoting away to AI and 00:21:34.700 --> 00:21:38.660 corners and sand chain, then that vision might 00:21:38.660 --> 00:21:41.240 be inconsistent with what the Metaversity Campus 00:21:41.240 --> 00:21:46.180 was doing for SIP33. I can understand that. The 00:21:46.180 --> 00:21:49.140 Metaversity Campus was more about VoxEdit and 00:21:49.140 --> 00:21:51.779 GameMaker and bringing people into the sandbox 00:21:51.779 --> 00:21:55.220 metaverse, which is now changing. And then SIP26. 00:21:56.559 --> 00:21:58.960 was the NFT collection management for the Sandbox 00:21:58.960 --> 00:22:02.440 DAO. This is Arthmore and his team. They were 00:22:02.440 --> 00:22:06.720 strategically realigning the 1 ,000 assets for 00:22:06.720 --> 00:22:09.720 the Sandbox NFT's collection. It was worth about 00:22:09.720 --> 00:22:12.920 1 ,000 ETH. And I don't understand why they stopped 00:22:12.920 --> 00:22:15.980 this one as well, because Arthmore, while they 00:22:15.980 --> 00:22:19.279 were funded by the DAO, they were successfully 00:22:19.279 --> 00:22:23.559 earning and paying their own bills with the realignment 00:22:23.559 --> 00:22:27.369 that they were doing. They had sold... and liquidated 00:22:27.369 --> 00:22:32.150 about $400 ,000 worth and returned it back to 00:22:32.150 --> 00:22:34.970 the DAO so that it could either require different 00:22:34.970 --> 00:22:37.910 sorts of art that's more culturally aligned with 00:22:37.910 --> 00:22:41.150 the sandbox, or if the DAO wanted to keep that 00:22:41.150 --> 00:22:44.329 money and repurpose it, then that was all part 00:22:44.329 --> 00:22:50.430 of the SIP to make as a community decision. Now 00:22:50.430 --> 00:22:54.099 that the sandbox is taking over, then, or the 00:22:54.099 --> 00:22:56.180 SIP would propose that the sandbox takes over 00:22:56.180 --> 00:22:59.480 so they could repurpose that as they need to. 00:23:00.380 --> 00:23:03.359 They were highly successful in meeting all of 00:23:03.359 --> 00:23:05.779 their target goals and objectives. So I'm not 00:23:05.779 --> 00:23:09.700 sure why they stopped this one either. Yeah, 00:23:09.759 --> 00:23:12.940 so I wish they had given that one a bit more 00:23:12.940 --> 00:23:15.279 thought, or maybe they did, but there's some 00:23:15.279 --> 00:23:18.460 reasons they're just not sharing. I gave them 00:23:18.460 --> 00:23:20.319 that feedback as well. I'm not sure why they 00:23:20.319 --> 00:23:24.369 wanted to do that. but there it is. It's still 00:23:24.369 --> 00:23:28.390 in the SIP after the discussion period. All right, 00:23:28.390 --> 00:23:30.390 the next part that caught my eye was when it 00:23:30.390 --> 00:23:32.369 talked about the Sandbox ecosystem is rapidly 00:23:32.369 --> 00:23:34.829 evolving and the types of initiatives supported 00:23:34.829 --> 00:23:36.690 by the DAO is not clearly aligned with those 00:23:36.690 --> 00:23:42.589 changes. Okay, great. That's fine. This SIP authorizes 00:23:42.589 --> 00:23:45.849 the termination and cancellation of other SIPs, 00:23:45.849 --> 00:23:51.599 so that means you're already evolving. So even 00:23:51.599 --> 00:23:53.579 if you continue the DAO, you can still cancel 00:23:53.579 --> 00:23:56.039 and terminate those SIPs if you really wanted 00:23:56.039 --> 00:24:00.160 to and still keep the DAO going. So it's not 00:24:00.160 --> 00:24:03.259 quite clear to me why this would lead us to wanting 00:24:03.259 --> 00:24:07.339 to pause the DAO where we already have a clearly 00:24:07.339 --> 00:24:11.839 defined restriction mechanism for new commitments 00:24:11.839 --> 00:24:15.099 and this SIP would authorize a termination and 00:24:15.099 --> 00:24:17.660 canceling of other SIPs. You could still continue 00:24:17.660 --> 00:24:20.619 the DAO. So even if it's rapidly evolving, the 00:24:20.619 --> 00:24:22.980 community now can no longer rapidly evolve with 00:24:22.980 --> 00:24:26.420 it because it is now being paused and we can't 00:24:26.420 --> 00:24:28.799 vote on anything new. Governing bodies are being 00:24:28.799 --> 00:24:32.559 stopped. So that part doesn't make any sense 00:24:32.559 --> 00:24:35.900 to me. And the next one was, a consolidated status 00:24:35.900 --> 00:24:39.220 table will document outcomes SIP by SIP. Thank 00:24:39.220 --> 00:24:42.019 you, thank you, Cyril and the DAO admin team 00:24:42.019 --> 00:24:44.539 for doing this. I'm looking forward to seeing 00:24:44.539 --> 00:24:48.250 this table. I have something on my own. that 00:24:48.250 --> 00:24:50.630 I put together that I'll be doing in my next 00:24:50.630 --> 00:24:53.210 episode, where I do a review of the entire sandbox 00:24:53.210 --> 00:24:57.509 DAO before, if this vote passes with a yes, then 00:24:57.509 --> 00:25:00.450 it'll be one of the final episodes, I imagine, 00:25:00.549 --> 00:25:04.369 where we just do a review of the sandbox DAO 00:25:04.369 --> 00:25:07.069 in its entirety. And so this consolidated table 00:25:07.069 --> 00:25:09.410 will really help with that. But I think it's 00:25:09.410 --> 00:25:11.369 great that they're doing this because it kind 00:25:11.369 --> 00:25:13.349 of gives a little bit more transparency into 00:25:13.349 --> 00:25:17.490 how the DAO has done and what steps it's taken 00:25:18.000 --> 00:25:21.420 from SIP 1 all the way to SIP 39. So thank you. 00:25:21.539 --> 00:25:25.559 Thank you very much for doing that. And then 00:25:25.559 --> 00:25:27.819 the next thing is transition operations to the 00:25:27.819 --> 00:25:32.720 sandbox team. That one is a little bit dicey 00:25:32.720 --> 00:25:35.319 because the sandbox team was already involved. 00:25:35.519 --> 00:25:41.420 I think the more we learn about SIP 39 and people 00:25:41.420 --> 00:25:43.599 who've been paying attention to the DAO knows 00:25:43.599 --> 00:25:46.339 that the sandbox team has had quite a bit of 00:25:46.339 --> 00:25:49.900 involvement. Thus far. So transitioning operations. 00:25:50.279 --> 00:25:54.720 To the sandbox team. Right now. It just seems 00:25:54.720 --> 00:25:59.859 kind of like. Like a way for them to. Push it 00:25:59.859 --> 00:26:01.660 to the side. Which is one of the risks that they 00:26:01.660 --> 00:26:06.220 mentioned. And I'll get into. What I thought 00:26:06.220 --> 00:26:08.420 about that. Because there's one sentence there. 00:26:08.460 --> 00:26:12.000 That I had flagged. But it looks like a way for 00:26:12.000 --> 00:26:15.339 the sandbox team. To kind of push it to the side. 00:26:15.480 --> 00:26:17.319 And not really acknowledge it. the community 00:26:17.319 --> 00:26:19.779 on this one. And the only reason I say that is 00:26:19.779 --> 00:26:22.099 because I've been in sandbox community for quite 00:26:22.099 --> 00:26:25.420 a while. And the Dow was one of the first ways 00:26:25.420 --> 00:26:28.400 that a lot of community members felt like we 00:26:28.400 --> 00:26:32.059 could have a say in the sandbox journey and really, 00:26:32.140 --> 00:26:38.559 um, participate and in the discussion and the 00:26:38.559 --> 00:26:40.700 decision -making, even though we didn't have 00:26:40.700 --> 00:26:43.940 any representation too much in the sandbox, uh, 00:26:44.019 --> 00:26:47.140 special counsel or the advisory board, because 00:26:47.140 --> 00:26:50.599 they were company -nominated, which is why this 00:26:50.599 --> 00:26:54.980 part stuck out to me, we were looking forward 00:26:54.980 --> 00:26:57.519 to the elections to where we could nominate community 00:26:57.519 --> 00:27:00.839 members, and it's a bummer that the pausing of 00:27:00.839 --> 00:27:04.980 the DAO proposes a pausing of the governance 00:27:04.980 --> 00:27:09.460 bodies, like advisory board and special counsel. 00:27:09.839 --> 00:27:13.400 Seb and I talked about this in Sandow 68, where 00:27:13.400 --> 00:27:16.549 I asked him what was... What was his understanding 00:27:16.549 --> 00:27:18.890 of why that was happening? He gave some really 00:27:18.890 --> 00:27:22.130 encouraging answers. I still don't like the fact 00:27:22.130 --> 00:27:25.089 that SIP39 is doing this, but it was helpful 00:27:25.089 --> 00:27:28.750 to hear Seb talk about it. Yeah, for what it's 00:27:28.750 --> 00:27:32.309 worth, I understand. I still disagree with that 00:27:32.309 --> 00:27:35.329 as part of SIP39, which is one of the reasons 00:27:35.329 --> 00:27:37.670 why I voted no. I want to continue the sandbox 00:27:37.670 --> 00:27:44.420 now. Okay. So the next thing that stuck out to 00:27:44.420 --> 00:27:46.880 me was where it said, Thus, any future activity 00:27:46.880 --> 00:27:49.200 can be designed to meaningfully support creators, 00:27:49.380 --> 00:27:51.859 players, and builders in the context of the updated 00:27:51.859 --> 00:27:54.579 product vision. There's nothing about continuing 00:27:54.579 --> 00:27:58.099 the sandbox DAO that couldn't still do this. 00:27:58.599 --> 00:28:01.319 If we were to elect new special counsel and advisory 00:28:01.319 --> 00:28:05.420 board members who would then meet as a community 00:28:05.420 --> 00:28:08.160 each day and build in public, there's nothing 00:28:08.160 --> 00:28:14.730 that would stop us from... from designing and 00:28:14.730 --> 00:28:18.910 modeling our activity to support this new updated 00:28:18.910 --> 00:28:21.490 product vision. We would be in a better place 00:28:21.490 --> 00:28:24.809 to support the updated product vision because 00:28:24.809 --> 00:28:28.670 we're involved, because we can discuss and make 00:28:28.670 --> 00:28:31.789 our own decisions on community matters and retain 00:28:31.789 --> 00:28:35.529 people. But this SIP would pause all of that 00:28:35.529 --> 00:28:38.509 and we would just kind of be in receive mode. 00:28:38.650 --> 00:28:41.880 It'd be a one -way street. Kind of like it's 00:28:41.880 --> 00:28:44.440 been for a number of years, you've been involved 00:28:44.440 --> 00:28:48.559 in the community. Unfortunately, the Sandbox 00:28:48.559 --> 00:28:50.859 team has kind of been a one -way street, which 00:28:50.859 --> 00:28:53.119 is why so many people, including myself, loved 00:28:53.119 --> 00:28:55.599 the DAO because it offered us a two -way street. 00:28:55.900 --> 00:28:59.579 And I really enjoyed the DAO and so did many 00:28:59.579 --> 00:29:02.759 others. So I'd like to continue that because 00:29:02.759 --> 00:29:04.859 it's one of the few things we have where we feel 00:29:04.859 --> 00:29:08.500 heard as a community. The next thing that popped 00:29:08.500 --> 00:29:12.369 up in my... On my brain was when I read, by halting 00:29:12.369 --> 00:29:14.950 new SIP intake and funding decisions, the DAO 00:29:14.950 --> 00:29:17.309 avoids committing resources to initiatives that 00:29:17.309 --> 00:29:20.329 may no longer fit the evolving ecosystem. Again, 00:29:20.430 --> 00:29:25.190 I already went over this. The current SIP process 00:29:25.190 --> 00:29:29.450 where you must be invited by a DAO administrator 00:29:29.450 --> 00:29:33.130 or the DAO admin team in order to submit a SIP, 00:29:33.130 --> 00:29:35.349 and then it goes through a lengthy admin team 00:29:35.349 --> 00:29:39.079 review. Which one of my sips is still stuck in 00:29:39.079 --> 00:29:40.920 admin team review because of the lengthy back 00:29:40.920 --> 00:29:45.099 and forth. And it was just clear that I wasn't 00:29:45.099 --> 00:29:48.299 able to convince the DAO admin team to let it 00:29:48.299 --> 00:29:51.180 go to special counsel recommendation and then 00:29:51.180 --> 00:29:55.440 to vote. It was well supported. A lot of people 00:29:55.440 --> 00:29:59.339 wanted it. That's called the sand chest. But 00:29:59.339 --> 00:30:04.200 the DAO admin team did not let it pass their 00:30:04.200 --> 00:30:06.990 review. Because it had a lot of questions and 00:30:06.990 --> 00:30:09.410 it didn't like the dollar figure. There's a lot 00:30:09.410 --> 00:30:13.549 of things that they, a lot of back and forth 00:30:13.549 --> 00:30:17.109 on it. And I still feel that it was a good sip. 00:30:17.190 --> 00:30:19.849 It still is a good sip. It was very reasonable. 00:30:20.210 --> 00:30:22.630 However, the Dow and Mateen disagreed, so it 00:30:22.630 --> 00:30:28.410 didn't progress. So that's two steps that severely 00:30:28.410 --> 00:30:33.250 limits anyone's ability to get it to vote and 00:30:33.250 --> 00:30:36.819 for the Dow to commit. those resources to initiatives 00:30:36.819 --> 00:30:39.900 that no longer fits the evolving ecosystem like 00:30:39.900 --> 00:30:43.180 i said i think i've authored eight or nine sips 00:30:43.180 --> 00:30:48.700 and only four four of them went to vote three 00:30:48.700 --> 00:30:53.839 of them passed so one of them did not pass so 00:30:53.839 --> 00:30:57.220 this is already true uh and and doesn't need 00:30:57.220 --> 00:30:59.660 to pause the dow in order to make it any more 00:30:59.660 --> 00:31:04.240 true Okay, by limiting activity to only what 00:31:04.240 --> 00:31:06.339 is required for compliance and asset stewardship, 00:31:06.680 --> 00:31:08.900 more of the DAO's remaining resources are preserved 00:31:08.900 --> 00:31:10.900 for future use rather than consumed by ongoing 00:31:10.900 --> 00:31:13.920 operations. I think this is the real reason why 00:31:13.920 --> 00:31:17.779 this is happening. If I had to guess, and being 00:31:17.779 --> 00:31:20.559 in the community now for five years and the DAO 00:31:20.559 --> 00:31:26.900 for a year and a half, I think this... uh preserve 00:31:26.900 --> 00:31:29.539 for future use rather than consumed by ongoing 00:31:29.539 --> 00:31:32.099 operations is the real reason why they want to 00:31:32.099 --> 00:31:38.000 do it because the special council was was compensated 00:31:38.000 --> 00:31:43.640 127 or 120 000 sand per person that's times five 00:31:43.640 --> 00:31:47.420 then you have well the advisory board was pro 00:31:47.420 --> 00:31:50.599 bono so they were all not being paid at all but 00:31:50.599 --> 00:31:52.740 then you had to pay the director for the foundation 00:31:53.559 --> 00:31:55.660 You have to pay renewal fees, all those sorts 00:31:55.660 --> 00:32:00.380 of stuff. However, we already know that SIP 39 00:32:00.380 --> 00:32:08.079 is requesting $44 ,000, right? Yeah, $44 ,000. 00:32:08.420 --> 00:32:11.240 So we know that it's going to, at least they 00:32:11.240 --> 00:32:15.920 consider that to be the minimum activity needed 00:32:15.920 --> 00:32:20.720 to continue. So I'm not quite sure what they 00:32:20.720 --> 00:32:23.559 mean by asset stewardship. Maybe they're talking 00:32:23.559 --> 00:32:27.579 about the NFT collection that Arth Morton and 00:32:27.579 --> 00:32:31.119 his team have been successfully stewarding in 00:32:31.119 --> 00:32:38.119 SIP36. However, compliance, you can be compliant 00:32:38.119 --> 00:32:42.400 with what you had, but I think it's really about 00:32:42.400 --> 00:32:47.519 preserving the remaining sand for future use. 00:32:48.170 --> 00:32:50.130 which we heard from the Dow admin team that it's 00:32:50.130 --> 00:32:53.250 about $800 ,000 left in today's exchange rate. 00:32:54.309 --> 00:32:56.910 Which, if I did some reverse math, let's try 00:32:56.910 --> 00:33:02.930 that. So about 800 ,000 sand, and sand is currently 00:33:02.930 --> 00:33:11.809 8 cents. So it's about 10 million sand left. 00:33:12.450 --> 00:33:15.930 So if you had a special counsel, which had 120 00:33:15.930 --> 00:33:19.220 ,000 sand, times five people at six hundred thousand 00:33:19.220 --> 00:33:24.259 okay yep so that that looks like maybe a major 00:33:24.259 --> 00:33:26.079 reason why the governance bodies are being shut 00:33:26.079 --> 00:33:32.099 down or paused i rather because 800 000 sand 00:33:32.099 --> 00:33:38.900 at 0 .08 is 10 million maybe they think that 00:33:38.900 --> 00:33:43.619 the the 600 000 sand to pay special counsel is 00:33:43.619 --> 00:33:47.539 using too many resources for what they believe 00:33:47.539 --> 00:33:50.839 they'll get out of it. That to me is the best, 00:33:50.980 --> 00:33:57.460 the most, what's the word? Charitable explanation, 00:33:57.640 --> 00:34:01.880 I think, for that. And if that's true, okay, 00:34:02.079 --> 00:34:05.579 I guess I can understand that. That's an argument 00:34:05.579 --> 00:34:08.699 to be made. But up until this point, there are 00:34:08.699 --> 00:34:12.139 a lot of counterbalances to that that I've already 00:34:12.139 --> 00:34:16.030 described. And the last thing that I... while 00:34:16.030 --> 00:34:19.329 I was reading was, this will be supported by 00:34:19.329 --> 00:34:21.650 a specific service agreement between the foundation 00:34:21.650 --> 00:34:24.010 and the sandbox. I wonder if they're referencing 00:34:24.010 --> 00:34:27.090 the current service agreement or if this is a 00:34:27.090 --> 00:34:30.650 new service agreement. I think I came to understand 00:34:30.650 --> 00:34:33.650 that there was a specific service agreement to 00:34:33.650 --> 00:34:35.590 the foundation of the sandbox. I think that was 00:34:35.590 --> 00:34:38.110 mentioned in one of the forum posts or on X. 00:34:38.349 --> 00:34:41.710 Can't recall where exactly. But if this is a 00:34:41.710 --> 00:34:45.130 new service agreement, then... Uh, it's not clear 00:34:45.130 --> 00:34:50.250 to me why this support would be needed because 00:34:50.250 --> 00:34:54.789 the sandbox already had quite a bit of, of influence 00:34:54.789 --> 00:35:00.409 in the way the sandbox foundation ran. So, uh, 00:35:00.630 --> 00:35:03.409 I don't know. It's just kind of scratching my 00:35:03.409 --> 00:35:06.250 head a little bit about that based on what I 00:35:06.250 --> 00:35:09.130 know about the Dow. And we read everything about 00:35:09.130 --> 00:35:12.289 the Dow, all of the memorandums, all the, articles, 00:35:12.530 --> 00:35:15.949 the bylaws. We read the laws and the Cayman Islands 00:35:15.949 --> 00:35:18.250 surrounding it in our foundation miniseries. 00:35:18.409 --> 00:35:22.130 So we have a pretty good understanding of what 00:35:22.130 --> 00:35:25.489 would be necessary and what's required to be 00:35:25.489 --> 00:35:28.070 compliant. And additional service agreement is 00:35:28.070 --> 00:35:31.869 kind of puzzling for that. So I think this SIP 00:35:31.869 --> 00:35:35.550 kind of gives a little more questions than it 00:35:35.550 --> 00:35:39.889 does answers. But as you saw mentioned a few 00:35:39.889 --> 00:35:45.130 times in, In SIP 39, one of the risks that they 00:35:45.130 --> 00:35:48.469 were mitigating against was the confusion. And 00:35:48.469 --> 00:35:50.929 the mitigation was to communicate the scope clearly, 00:35:51.110 --> 00:35:54.570 they would run one structured AMA, which they 00:35:54.570 --> 00:35:59.489 did, exactly one. And then down below, in order 00:35:59.489 --> 00:36:02.849 to mitigate fragmented narrative across channels, 00:36:03.090 --> 00:36:06.170 a single forum thread and limited spokespeople. 00:36:06.349 --> 00:36:10.210 So there were, I think, two spokespeople on the 00:36:10.210 --> 00:36:16.849 forums. three spokespeople on the ama and other 00:36:16.849 --> 00:36:20.250 than communicating in the ama and a few messages 00:36:20.250 --> 00:36:24.650 on the forums there hasn't been much else to 00:36:24.650 --> 00:36:27.610 go off of for this sip it's just kind of like 00:36:27.610 --> 00:36:30.909 here it is now go vote but also the sandbox style 00:36:30.909 --> 00:36:34.010 is going to vote with its 27 million wallet so 00:36:34.010 --> 00:36:36.929 it's going to be difficult to overcome that i'm 00:36:36.929 --> 00:36:40.570 going to do my best now to get the word out and 00:36:41.309 --> 00:36:43.389 and make a case for why we should continue the 00:36:43.389 --> 00:36:48.050 DAO. And as I mentioned in Sandow67, which is 00:36:48.050 --> 00:36:51.050 my reaction to the DAO pause and the AMAs, and 00:36:51.050 --> 00:36:54.409 then Sandow68, I'm of the opinion we should continue 00:36:54.409 --> 00:36:58.230 the DAO. We can continue the DAO and still meet 00:36:58.230 --> 00:37:02.250 the vision and evolve with Sandbox 3 .0, and 00:37:02.250 --> 00:37:05.429 we can do so with our governing bodies. The community 00:37:05.429 --> 00:37:08.130 will feel more involved. It will be able to evolve 00:37:08.130 --> 00:37:13.360 faster. it will, I think it's the right decision 00:37:13.360 --> 00:37:16.860 to make. So I voted no in order to continue the 00:37:16.860 --> 00:37:23.559 DAO. And there we go. I think that covers it. 00:37:25.559 --> 00:37:30.019 Okay. So that was a read -through of SIP -39 00:37:30.019 --> 00:37:38.900 and some commentary right after it. I normally 00:37:38.900 --> 00:37:42.460 go through Sandbox Spaces, forums, on Discord, 00:37:42.940 --> 00:37:47.639 on Twitter, and on YouTube. Here are the things 00:37:47.639 --> 00:37:51.360 I normally go over. And on the X Spaces, there's 00:37:51.360 --> 00:37:54.139 these three things, Bulls on the Block, Coffee 00:37:54.139 --> 00:37:56.659 with Captain, and Well Members. We've covered 00:37:56.659 --> 00:37:59.880 them and interviewed most of them. And I'll take 00:37:59.880 --> 00:38:04.619 a quick peek at the Twitch, see if anyone is 00:38:04.619 --> 00:38:08.400 also hosting Sandbox so I can raid them. Maybe 00:38:08.400 --> 00:38:14.280 I'm the only one. I am. So I will raid friend. 00:38:16.239 --> 00:38:23.980 And then we will conclude today. So that was 00:38:23.980 --> 00:38:32.000 Sandow69, a SIP review of SIP39, which wants 00:38:32.000 --> 00:38:34.840 to pause the sandbox DAO. I read through it. 00:38:34.860 --> 00:38:37.260 I gave some commentary. Thank you all for your 00:38:37.260 --> 00:38:41.440 time and have a great day. See you in the metaverse.