Hey friends, and welcome to another biweekly update.This week, we’re focusing on two topics:<ol><li>a small update regarding our progressive web app (PWA) wallet, and</li><li>a cautionary tale about the dangers of web3, and how our wallet incorporates multiple safety features to hopefully make web3 a safer place for you.</li></ol>&nbsp;<h1 style="margin-left:0px;">Progressive Web App (PWA) Wallet</h1>For those who remember, about a month ago, we’ve talked about the App Team doing this:<blockquote>The App Team is busy at work doing lower-level, architectural refactoring this week. This is due to an ongoing plan to make our wallet-related services available not just as a native app running on iOS and Android, but also as a progressive web app that can run on virtually any platform with a standards-compliant browser.</blockquote>Yep, sounds cool. It’s been a month since, our PWA wallet is still cooking, and here’s a sneak peak of what’s already done:<ul><li>Added a splash screen to the PWA wallet.</li><li>Users with a KryptoGO account can login to the PWA wallet.</li><li>Users are able to see their NFT collection in the PWA wallet.</li><li>Users are able to send tokens in the PWA wallet.</li><li>News users can create a wallet in the PWA wallet.</li><li>New users can import their existing wallet in the PWA wallet.</li></ul>We <a href="https://pwa-dev.kryptogo.com/onboard">offer a demonstration here</a> of how the PWA wallet may work. However, note that this is but a prototype and things are prone to break — use it at your own risk. If you have any ideas or feedback, let us know!&nbsp;<h1 style="margin-left:0px;">A Cautionary Tale</h1>As audacious pioneers navigating the treacherous waters of web3, it is inevitable from time to time we stumble upon sharks with great white teeth.Dangerous fish, and even more dangerous “<a href="https://en.wikipedia.org/wiki/Phishing">phishing attacks</a>.”Every time news <a href="https://finance.yahoo.com/news/did-mark-cubans-wallet-just-123000799.html">like this one</a> (Did Mark Cuban’s wallet just get drained?) pop up, the pioneers tremble in fear, a sharp feeling of deja vu stabbing us like a cold arrow in the back.Drained wallets. Lost cryptocurrency. Scams. Social attacks. Cyber attacks. Phishing attacks. Fake websites. Dodgy links. Compromised private keys. Malicious contracts. I could go on, but you get the idea.From the same article, quote,<blockquote>Phishing has proven to be a very popular and lucrative scam for fraudsters. The FBI’s Internet Crime Complaint Center (IC3) received <a href="https://www.fbi.gov/contact-us/field-offices/springfield/news/internet-crime-complaint-center-releases-2022-statistics">800,944 complaints in 2022</a>, with losses exceeding $10.3 billion.</blockquote>The question to ask then, is, what can we do to minimize risk as a web3 pioneer?Of course, digital hygiene practices are important, and all crypto bros should know the basics of how to protect themselves — don’t click on shady links, don’t sign transactions you don’t understand, yada yada. Yet humans are prone to human error and lapses in judgement, so as wallet app developers, we want to do want we can to make our wallet as safe as possible.In particular, we want to implement additional protective measures in our wallet so that, hopefully, just before you make a bad decision, our wallet would show an alert, a message, an additional confirmation — anything — that would stop you for a few extra seconds that might just save you from losing all that BTC and ETH in your wallet.Here’s what our wallet does:<h2 style="margin-left:0px;">1) Spend approval warnings</h2>EIP-2612 is an Ethereum Improvement Proposal that introduces a method for token holders to give permission for their tokens to be spent by another address through a signed message, rather than an on-chain transaction. This feature is particularly useful for reducing transaction fees and improving user experience in decentralized applications (DApps).The key part of this standard is the <code>permit</code> function. It allows users to sign a message containing details like the spender's address, the amount they're allowed to spend, and a deadline for this permission. This signature is then used by the spender to interact with the token contract, effectively allowing them to transfer the token without requiring the token holder to send a separate transaction.In a scam scenario, a malicious actor could trick a user into signing a message with the permit function that unknowingly gives the scammer approval to transfer all of the user’s tokens. Our wallet detects when the user would be signing a message that approves spending their tokens, and warns the user. This is usually not something you want to do, unless you know explicitly who and what you’re approving.<h2 style="margin-left:0px;">2) High-risk website warnings</h2>KryptoGO Wallet automatically monitors high-risk websites and transactions using top services such as MetaMask, Phantom, Blowfish, Solfare, PhishFort, and ScamSniffer. If you’re opening or even connecting to a scam webpage, we’ll do our best to let you know before anything bad happens.<h2 style="margin-left:0px;">3) Remote Procedure Call (RPC) simulation</h2>Remote Procedure Call (RPC) simulation allows users to simulate transactions before actually executing them on the blockchain. This means that you can test how a transaction would behave (like transfers, smart contract interactions, etc.) without actually making any changes on the blockchain. It’s a way to predict the outcome and potential issues of a transaction, such as running out of gas or encountering errors in smart contract execution.Before you sign any transaction, look at the RPC simulation first. If the simulation shows that your wallet is going from 10 ETH to 0 ETH — don’t sign the transaction.We’re continuously putting effort into making our wallet safer. Hopefully, these safety features will make web3 and crypto transactions a safer place for all of us.&nbsp;<h2 style="margin-left:0px;">Wallet Improvements and Bug Fixes</h2><ul><li>Added an “online” indicator and “message-read” indicator in Chatrooms.</li><li>Fixed a bug where the “Send” option would not appear for certain friends.</li><li>Fixed a bug where the default wallets of certain friends would not update in time.</li><li>Fixed a bug where friends added via QR code would not show up if the user hasn’t granted phone contact permissions.</li><li>Fixed a bug where setting a password would reset the same user’s vault data on the server.</li></ul><h2 style="margin-left:0px;">Security Improvements</h2><ul><li>Applications which pass user supplied URLs to be opened by the operating system are frequently vulnerable to code execution with user interaction. We now allow only http and https protocols in our dApp browser in order to prevent arbitrary code execution.</li><li>Removed unused 3rd party API keys and dependencies.</li><li>Added App Transport Security (ATS) to iOS. From <a href="https://developer.apple.com/documentation/bundleresources/information_property_list/nsapptransportsecurity/">Apple’s developer documentation</a> :</li></ul><blockquote>ATS improves privacy and data integrity for all apps and app extensions, and requires that all HTTP connections made with the <a href="https://developer.apple.com/documentation/foundation/url_loading_system">URL Loading System</a> use HTTPS. It further imposes extended security checks that supplement the default server trust evaluation prescribed by the Transport Layer Security (TLS) protocol. ATS blocks connections that fail to meet minimum security specifications.</blockquote><ul><li>We now use dynamic salt (instead of static salt) for hashing and encrypting sensitive data on the client side. This means that a unique and random salt value is generated for each operation and for each piece of data that requires hashing or encryption.</li></ul>&nbsp;That’s it for this week!Have feedback, or encountered any issues with any of our products? Don’t hesitate to contact us via Discord, or via any of our other social media links listed below.See you in two more!<h1 style="margin-left:0px;">Follow us:</h1><a href="https://discord.gg/kryptogo">Discord</a> | <a href="https://www.facebook.com/kryptogo">Facebook</a> | <a href="https://twitter.com/kryptogo_">Twitter</a> | <a href="https://instagram.com/kryptogo_">Instagram</a> | <a href="https://www.linkedin.com/company/kryptogo/">LinkedIn</a> | <a href="https://t.me/kryptogocom">Telegram</a>

This week, we talk about the latest update to our PWA wallet, as well as a cautionary tale about wallet safety.

Biweekly Dev Update: December 13th, 2023

Beginner's Guide to Hyperliquid ft. KryptoGO App: Feb 12, 2025

Refining the Waves with Ocean v3: January 22, 2025

Biweekly Update: January 8th, 2025

The '25 Roadmap Preview: December 18, 2024

“The King of Tron” Update: December 4, 2024

Biweekly Update: November 20, 2024

The 'Pulse' Update: November 6, 2024

In-Depth Technical Analysis: Why Choose a Mature Crypto Wallet Service Instead of Building Your Own

Five Stages of Evolution for Crypto Wallets

Biweekly Update: October 23, 2024

Biweekly Update: October 09, 2024

Biweekly Update: September 25, 2024

Send Via Link campaign and "Gimme more wallets" Update :  September 11, 2024

The “Send Crypto via Link” Update: August 28, 2024

KryptoGO's Award-Winning Innovations at ZK Hack Montreal, ETHDenver, and ETHTaipei

Stake Your Stables! Biweekly update: August 14, 2024

The “Not Just A Wallet” Update: July 31, 2024

Biweekly Dev Update: July 17, 2024

Biweekly Dev Update: July 3, 2024

Biweekly Dev Update: June 5, 2024

Challenges and Solutions for Using Cryptocurrency in Business Operations

Biweekly Dev Update: May 22, 2024

Biweekly Dev Update: May 8th, 2024

Biweekly Dev Update: April 17th, 2024

Biweekly Dev Update: April 3rd, 2024

Biweekly Dev Update: March 20th, 2024

Making Sense of Decentralized Wallets: EOA and Smart Contract Explained

Biweekly Dev Update: March 6th, 2024

Centralized vs. Decentralized: The Ultimate Guide to Choosing the Right Crypto Wallet for Your Business

Navigating Compliance in Taiwan's Cryptocurrency Market: From Fraud Prevention to Enhanced Regulation

【Kind Reminder】Please be vigilant against scams. KryptoGO will never proactively ask you to make investment transactions.

Biweekly Dev Update: February 21th, 2024

Biweekly Dev Update: February 7th, 2024

Web3 Business Operations: Future Trend or Current Necessity?

Biweekly Dev Update: January 24th, 2024

Biweekly Dev Update: January 10th, 2024

Biweekly Dev Update: December 27th, 2023

Biweekly Dev Update, November 29th, 2023

Biweekly Dev Update, November 15, 2023

Biweekly Dev Update: November 1st, 2023

Biweekly Dev Update: October 19th, 2023

Biweekly Dev Update: Oct 4th, 2023

The Chatroom and Social Update: September 20th, 2023

Play-to-Earn vs. Blockchain Gaming: Rediscovering the Joy of Play

Product Launch Update: September 6th, 2023

KryptoGO Launches AI-Powered One-Stop Web3 Cloud Solution

Biweekly Update: August 23rd, 2023

The Keyless Wallet Update: August 9th, 2023

Biweekly Update: July 26th, 2023

Biweekly Update: July 12th, 2023

Biweekly Dev Update: June 7th, 2023

Unlock the Future: Passkey + DID + FIDO - Exploring the Next Generation of Digital Wallets and Identities

Biweekly Dev Update: May 24th, 2023

Biweekly Dev Update: May 10th, 2023

Biweekly Dev Update: April 26th, 2023

KryptoGO team wins three ETHGlobal Tokyo Hackathon Awards! Join hands with YGG Japan and IVC to lay out GamiFi industry

Biweekly Dev Update: April 12th, 2023

Help enterprises enter the Web3 world painlessly! What is WaaS?

Biweekly Dev Update: March 22th, 2023

How Much Does It Cost to Develop a Cryptocurrency Wallet on Blockchain?

How to Navigate the Metaverse: A Guide to 7 Different Types of Crypto Wallets

Virtual asset transaction service KYC, AML demand increased! KryptoGO Compliance work with Gaia Information  pioneered regulatory investigation engine

Biweekly Dev Update: March 8th, 2023

DeFi and KYC: Conflict or Coexistence?

Biweekly Dev Update: February 22nd, 2023

KryptoGO Wallet Updates: Supports Ronin chain, Personal Profile, Wallet Connect 2.0

Biweekly Dev Update: February 8th, 2023

Biweekly Dev Update: January 18th, 2023

Coinbase, the most compliant exchange, has been fined $100 million by the government and given a deadline to fix it.

Biweekly Dev Update: January 4th, 2023

Biweekly Dev Update: December 21, 2022

Biweekly Dev Update: December 7th, 2022

Biweekly Dev Update: November 23rd, 2022

Why can't you get your crypto assets back when the FTX exchange collapses? – Not Your Key, Not Your Coin

Biweekly Dev Update: November 9th, 2022

Biweekly Dev Update: October 26th, 2022

Biweekly Dev Update: October 12th, 2022

Biweekly Dev Update: September 28th, 2022

Things you should know about financial security in the Web3 era: How does token, private key, and wallet (account) work?

Collaboration for Web3 Game Wallets: YGG Japan, KryptoGO, and IVC Join Forces

Biweekly Dev Update: September 14th, 2022

Wanting to issue NFT but is complained about the difficult procedure? —Find out what the marketing pain points are from the “distribution process”

Biweekly Dev Update: August 31th, 2022

Crypto Wallets: Custodial vs. Non-Custodial Wallets

All You Need to Know About VASP FATF

Biweekly Dev Update: August 17th, 2022

Taiwan-based KryptoGO Secures US$3M in Seed Funding

Biweekly Dev Update: August 3rd, 2022

FATF Methodology with the Rapid Development of Virtual Assets 

How to regulate virtual assets? –about FATF Travel Rule recommendations

Different transaction monitoring mechanism between Fiat and Crypto

Biweekly Dev Update: July 20th, 2022

The difference between KYC & AML?

Always being a concern in the bank? Get to know “KYC” in 5 minutes

Biweekly Dev Update: July 6th, 2022

test 123123

Biweekly Dev Update — 20220622

Biweekly Dev Update — 20220608

Biweekly Dev Update — 20220525

Biweekly Dev Update: December 13th, 2023

Recommend Articles

Hot Articles

Hot Tags