safe-smart-account VS FirebaseRTC

Recently, I had a chance to work on an interesting task where I needed to integrate the Gnosis Safe multi-signature wallet into the existing application.

Resolv's Protection Protocol™ would implement the highest level of security on all fronts. Our multi-sig wallet is created using Gnosis Safe's industry-standard infrastructure. The keys for said wallet would be distributed amongst the most trusted players in the space (i.e. Kleros, Polygon). This is done so that no one party has full control over the custodian wallet holding everyone's assets. As a result, our customers can rest easy knowing that not one person could run away with the entire pot. We'd also use AES 256-bit encryption to make sure user data is kept safe and inaccessible by third parties.

Prefer self-custody. If you don't feel comfortable, then start with small amounts on a trusted CEX (Coinbase eg.) and then move to self custody. A wallet should be open-source, audited, offers security bounties, is Battle -tested and easy to use. For small funds, use metamask. For big funds use hardware wallet, https://airgap.it (with old Smartphone/device) or a smart contract multi-signature wallet (https://safe.global).

There is the exception of https://safe.global though.

Here a few links in case you want to try out some different wallets: * https://safe.global * https://metamask.io * https://trezor.io * https://onekey.so * https://keyst.one

But if you insist, you can use https://airgap.it or http://safe.global. There the company influence is much less

Self-custody on https://safe.global wallet. Safe Wallet is the gold standard for large funds on EVM-compatible chains. It's audited, open-source, bad bounty programs, battle tested, supports virtually all defi and has multi-sig. What more to you want? Ah, did I forget to mention, that it is formally verified and had the correctness of the smart contract code proven? 😎

If you're only holding coins and not moving them frequently, then a paper wallet might be good. Just generate your seed phrase and address in an air-gapped device (e.g. old phone) and send ETH to that address. If you want a bit more flexibility of usage you can use https://airgap.it or an hardware wallet such as Trezor, Keystone or OneKey. And the ultimate gold standard is to use a Safe Wallet (https://safe.global). It's a multi-signature wallet and is even formally verified to be correct. It's the best choice atm.

Or even better just https://safe.global for a secure, audited, formally verified, battle tested and open source smart contract multi-signature wallet. It has arguably the best security guarantees you can have atm.

WebRTC it is: https://webrtc.org/

Yes only the network layer encryption. No file encryption as it will cost client browsers a lot in case of encrypting and then decrypting that at other end.

I have written more about it here: https://dikshantraj2001.medium.com/nat-stun-turn-and-ice-466...

Currently, I am using the public STUN servers only. If the IPs are not reachable, it would show an error and won't work as setting up TURN server would mean same as a third party server saving in file and serving it over network

You might also consider assessing complementary or alternative technologies; WebSocket and HTTP aren’t the only options when it comes to real-time communication, after all. WebRTC is similar to WebSocket, with the key difference being that it’s used to implement peer-to-peer connections without relying on a server. That can be especially helpful for video calls, allowing participants to communicate directly without introducing load to your server.

We use WebRTC to gain access to a user’s camera and microphone using the getUserMedia method. Typically, I would gain access to both of these from the same call. However, our experience requires the camera to flip from facing the environment to facing the user and I noticed that the small period of time the flip occurred (and microphone wasn’t available) contributed to a bit of audio lagging in the final recorded video. This was one of the nastier bugs I faced in development. So, we’ll just access each of these on their own media streams so that the camera can flip independently from the microphone.

Low latency streaming (<500ms): The Video SDK's infrastructure is built with WebbRTC, which helps to deliver secure and ultra-low latency video streams to all audiences at different bandwidths.

Web Real-Time Communication (WebRTC) is a technology developed by Google in 2013 for peer-to-peer communication. WebRTC enables web browsers to capture audio, video, exchange data, and teleconferencing without plugins or intermediaries. WebRTC achieve these through APIs and protocols that interact with one another. WebRTC media streaming when used with SocKet.IO will produce an application that streams media and exchange data instantly. Socket.IO is a library that provides low latency bi-directional communication between client and server. Socket.IO was built on websocket, a communication protocol that provides a full-duplex and low latency communication between server and browser. In this article, readers will learn how to build a video chat application using WebRTC and Socket.IO. This article is for web developers who wish to develop web applications that can stream media between two peers of computers in real-time without installing any plugins.

Possibly you what to look into WebRTC: https://webrtc.org/

Use the language you're comfortable with. Sounds like you're interested in creating a blockchain game. Writing your own simple game engine isn't simple. I would recommend utilizing an existing one for whatever language you want. If you still choose to write your own it can be a valuable lesson in graphical programming which I personally find fun. It's easier to cheat a webpage embedded game written in Javascript than one ported to WebASM in my experience and I've heard good things about WebRTC for embedded multiplayer games.

Have you looked into WebRTC? https://webrtc.org Seems like it supports exactly what you're looking for. SignalR is more for real-time messages, not really for streaming.

P2P is nothing new. It is a long-established means of connecting two or more people directly over a network. Web browsers are very capable of a wide range of P2P connections. Many apps use WebRTC to enhance realtime apps, but it is still an underutilized technology. Even with WebRTC, many apps are designed around the dependence on a central app server with WebRTC performing a user experience enhancement. Web meshes turn this idea on its head: Instead of using P2P connections to enhance the user experience, what if P2P connections were the foundation of the user experience? In other words, what if there was no central server?