A SAFETYNET NEWS FLASH:

We will hold our traditional Sunday meeting at 20:00 hrs. CET time in the @vibehut room: https://vibehut.io/rooms/63fbbf21573f450014f7d706

Meeting Details:
•	Date: Sunday, December 22nd
•	Time: 20:00 - 22:00 CET
•	Attendees (listed below)

Agenda:
1.	Opening
2.	Confirming Previous Meeting Minutes
3.	Meeting & Greeting New Attendees
4.	Code of Conduct & proposed update (item brought in by @stargeezer)
5.	Server Status Reports (Validator, Consensus, Tech, Oracle)
6.	Proposal Maker testing is underway. Some bugfixes are being done.
(the voting pyramid will be upon the Proposal Maker in the near future)
7.	Legal Entity Update
8.	Subcommittees: Marketing & Storage Solutions
9.	Other Topics: Node Construction Workshop
10.	Closing

Meeting Highlights:
Server Status Reports:
Software Updates:
Legal Entity Update:
Subcommittees:
•	Marketing subcommittee is in action and meets Wednesdays at 20:00 CET (first meeting coming up January 8th
•	Storage Solutions subcommittee formation is pending node operator response. Open forum will be held on Saturday at 20:00 CET, December 28th (second meeting).
Other Topics:
Closing:




@SafetyNet is a project that aims to facilitate the @Deso blockchain

The @Safetynet project creates a system of redundancy for the @DeSo ecosystem with a secure decentralized network owned and operated by the community. 
The @SafetyNet project is a project started by members of @theDC.

Our main objectives are:
A.	Securing the blockchain by providing redundancy in all key components of the @DeSo blockchain
B.	Making sure all user content will stay safe at any time and regardless of any unfortunate incident occurring.
C.	Decentralizing the @DeSo blockchain by providing extra servers and all related services so we all are not depending on one single or few point(s) of failure.
D.	Building the @DeSo ecosystem by collaborations with and support to all members of the @DeSo community (individuals, node operators and developers)
E.	Testing the resilience of the @DeSo blockchain
F.	Adding functionality to the blockchain by providing on chain software solutions.

Our frontend application is ready for your use
https://safetynetvalidator.nl 

If you have any questions, you can email them at: support@safetynet.social
You may also contact us by sending us a post addressed to @safetynet
Make your own help ticket or use our help database and Q&A: https://safetynet.freshdesk.com/support/home

Learn more about @Safetynet and read our white paper: https://1drv.ms/w/c/a946bc8fcce09f1a/EdnhOleOVUNIrQqIiylcm8EBdqf-HDLZ88YhaIVUSkNCkw


our servers are:

1.	Validator server https://validator.safetynet.social

2.	Consensus server https://consensus.safetynet.social

3.	Tech server https://tech.safetynet.social

To see the real-time performance of all @DeSo services, check: 
https://status.safetynet.social/status/deso

To support our project, go to our Open Fund page and then click the trade to purchase available tokens. openfund.com/d/SafetyNet
We use @openfund to keep a transparent ledger of all our financial dealings.
Also contributors might be appreciated in the future

You can also contribute to the project by staking with our validator.
Stake on:  @SafetyNetValidator 

SafetyNet is designed and developed by @Carry2Web , @Diamondthumb , @DegenDoge, @that70srobot, @ouwepiet, @erwinwillems, @studio_richards, @nathanwells, @stevonagy and @arnoudvanderplas 

What is the project @SafetyNet ?
It is a community project set up by members of @TheDC
The project has the following objectives:

1. Strengthening the @Deso blockchain:

HOW?: We will provide a minimum of three extra servers (nodes / validators) to the @Deso blockchain.

WHO?: The community will own these servers. No person has solo control. By this, YOU ALL will be owning these servers (if you join our communal moment)

WHY?: By providing these servers, we will make sure the chain will be more stable, secure and resilient. No single server will provide services. No single person or centralized entity owns the server /hardware. No single person or entity owns the supporting funds. By these facts, the project @SafetyNet will assure ALL community members can always use @Deso even when all other servers go down.

2. Transparency:

HOW?: We will keep you updated and informed about all activities.
We will keep a ledger of our costs (payment for servers our work will be free atm) and incomes (for now our team money and donations).
We will keep you informed as well as possible about the execution of the project. Furthermore, we will make an effort to inform the community (targeted at technical and non-technical people) about what we are and will be doing.

WHO?: You are our community members, fiends, and we will treat you as valued customers to be cherished. We will communicate transparently to you at all times. We will be frequent, engaging and understandable in our communication.

WHY?: YOU have to carry our project, we have no project without you! If we are transparent with you, we hope and believe you will discover the @SafetyNet project is worth your support and possibly your financial support.

3. Collaboration with the community members, developers, node runners, server owners, validators and application owners:

HOW?: We want to openly communicate and engage with ALL parties involved with @deso. We want to form alliances and communication platforms between all parties involved.
Working transparently together, we will get further and gain trust in and outside of @Deso

WHO? We @TheDC members in the @SafetyNet will actively pursue communication with all parties involved with @Deso.

Why?: We want to gain more communication going in the @Deso "sphere". The communications between community members, developers, node runners, server owners, validators and application owners has to be improved. Especially the communication top down has to be improved. As community members ourselves, we feel there is much room for improvement

4. Adding value to @DeSo:

HOW?: We want to ask all parties actively for input, critique and Ideas for the operation of nodes, servers, validators and applications on @Deso.

WHO?: We, the members of the @safetynet project people and @TheDC in general, will try to round up all thoughts from the entire community passively and actively.

WHY?: Many opportunities in @Deso are overlooked or side stepped because there is little communal engagement between community members, developers, node runners, server owners, validators and application owners. This situation can be improved upon.

I hope you found this description somewhat informative. We would as the @safetynet project group appreciate your critique, suggestions, additions and comment on:
1 This text (is written bad, oke, so-so, great)
2. It's content
3. It's meaning to you
4. What do you want in relation to our project?
