Komodo team member smk762 guides us through the 0.5.4 version of atomicDEX wallet.

The atomicDEX wallet has added 13 new protocols since this video was created, so there's even more to see!

The atomicDEX page shows the most recent commits & issues, so there's an easy way to see what the developers of the most versatile multi-protocol wallet have been up to from their work pushed to github.

@everyone Announcing v0.9.2-3, NON-MANDATORY, FOR MAINNET -- CRITICAL FOR TESTNET USE This release has no mainnet changes.

New use cases live on testnet

- Ability to create new .veth VerusIDs that are priced in USDC, paid for using $100 woth of Bridge.VETH, and useful as both self-sovereign VerusIDs and also to define Ethereum mapped currencies for use on Verus, Ethereum, and PBaaS chains across the network. While this was previously in the protocol, we will shortly roll out the Etherum bridge update that will let everyone easily use it.

- Full support for defining mapped currencies and easily exporting any PBaaS currency as an ERC20 to Ethereum's Rinkeby testnet. Using mapped currencies, you can even create your own provable, auditable, mapped stable coins, collateralized 100% provably by the protocol, using any ERC20 currency on Ethereum, such as DAI, USDC, or any other currency at all. Either root VerusIDs or.veth IDs can be used to create Ethereum mapped currencies.

- Ethereum bridge website now recognizes and makes it easy to use all exported, ERC20 PBaaS currencies and all mapped currencies in the new user interface.

With v0.9.2-3, and the soon to be launched update to the ETH bridge, ready now and expected on testnet within the next couple days, you can now create .your own, self-sovereign, permanent name.veth identities, and map currencies to them. For example, MYCOIN.VETH could be mapped to USDC, creating a fully decentralized, provable, auditable, currency that can be sent back and forth from Ethereum's USDC to Verus or any PBaaS chain as MYCOIN.VETH. You can do the same with any currency on Etherum and any identity you control that is either a root or *.veth VerusID.

The rest of these release notes are the same as the prior release. Drop by pbaas-development to help get PBaaS ready for mainnet!

CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.2-3

GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.2-3

https://discord.com/channels/444621794964537354/449633429198340106/977409116362395699

Hello @everyone

We promised and we are delivering! Thank you to all TKL supporters for helping us kickstart the project and for your continuous contribution.

This release includes long awaited Time Lock transactions changes.

Download this release to see your time lock rewards: https://tokel.io/

Check your rewards at https://tokel.io/rewards/

Thank you again for supporting us and believing in us at early stages of the project

Features
- Added functionality for displaying time lock transactions
- NSPV-js updated to send/receive time lock transactions
- The main Dashboard is a Wallet now
- Added a widget to display token and TKL addresses at one place
- More organised history widget
- New Send Widget which shows the Spendable and Locked amounts depending on whether the user has locked transactions

Bugs
- Fixed incorrect TKL price on the main view of the dapp
- Fixed incorrect TKL amounts for transactions with decimals
- Extended transaction value parsing Please reach out to us if you have any questions 🤗

Thank you again everyone for being part of Tokel! Tokel Team

https://discord.com/channels/774497890025472010/807859586568421377/974839839394521088

@everyone

Ahoy Pirates!

The iOS Mobile Wallet is now officially released on the App Store! Special thanks go to the Meshbits Limited & Pirate Wallet team for tirelessly working and developing it over the past couple of months. Download the wallet here: https://piratewallet.io/

@everyone Announcing v0.9.1-2, OPTIONAL FOR MAINNET USERS, MANDATORY FOR TESTNET USE

v0.9.1-2 RESETS TESTNET -- THERE ARE NO MAINNET CHANGES

IF YOU HAVE ALREADY USED TESTNET WITH VERSIONS PRIOR TO v0.9.1-2, MAKE SURE TO DELETE AND CLEAR ANY EXISTING TESTNET DATA FOLDERS AS DESCRIBED IN THE LINKS BELOW.

The main reason for this update is that while the Ethereum contracts are in process of being made upgradeable, there are not yet fully so. After the Ethereum bridge deployment on the prior testnet, testing revealed an issue that required a change in the contract. It would either have caused us to take some number of days to workaround with a forking change for only the testnet, or do what we are doing, which is focus on the most efficient path to mainnet, take the testnet reset hit and move forward. We have initialized the new testnet basically the same as the last, except that the Ethereum bridge is already deployed and live, with the bridge converter currency, the one that will make it possible to convert between ETH and other currencies for fee crossing in its pre-launch phase and ready to launch at block 3000. You can certainly join the prelaunch with Ethereuum, Verus, or USDC that you may use the web interface (https://ethtest.verus.services/) and Metamask to send over from the Rinkeby testnet. During this prelaunch phase of the Ethereum bridge, and until block 3000, which is tomorrow morning PST, you may join the Bridge.vETH pre-launch and preconvert to the basket currency, using any of the reserve currencies, which in in this case, are ETH (Rinkeby), USDC (Rinkeby), and VRSCTEST. If you want to discuss with others, checkout the pbaas-development channel.

I want to thank everyone for all of the amazing testing and work being done on testnet, and we appreciate your understanding of this decision. Enjoy!

CLI release: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.1-2
GUI release: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.1-2

@everyone ANNOUNCING NON-MANDATORY, RECOMMENDED FOR MAINNET, MANDATORY FOR TESTNET PBAAS UPGRADE v0.9.1

Testnet Featuring Verus PBaaS -- The most powerful and interoperable currency, blockchain, and ERC20 launch, scale, and MEV-resistant DeFi platform to exist, all with no programming required!

v0.9.1 improves mainnet bootstrap and GUI backup/restore user experience but does not upgrade mainnet protocols and is not a required update for mainnet-only users. It is required to use the public testnet. IF YOU HAVE ALREADY USED TESTNET WITH PRIOR VERSIONS, MAKE SURE TO DELETE AND CLEAR ANY EXISTING TESTNET DATA FOLDERS AS DESCRIBED BELOW.

Verus PBaaS Features Live on v0.9.1 Testnet

- Provable or pseudonymous, identity-based currency, liquidity pool, NFT and multi-blockchain, fully decentralized network.
- On-chain 100% decentralized, launches with fair launch and/or crowdfunding options, on-chain auto-refund option for missed targets, automatic Ethereum ERC20 contract deployment, auto-created, MEV-resistant, liquidity baskets and even auto-bridged, merge mineable, fully independent rent-free PBaaS blockchain launches.
- All DeFi AMM conversions are verified via mining and staking as part of the L1 consensus protocol. All conversions in a single liquidity basket are calculated simultaneously for all transactions in any given block, meaning all participants get the same price in all directions of conversion, with a minimum conversion fee of 0.025% and a maximum of 0.05%.
- All currencies and identities are primitives at L1 and are validated and verified on UTXO transactions, which check all inputs and outputs just as single currency L1s, such as Ethereum or Bitcoin check the native currency inputs and outputs of transactions.
- All currencies on all independent connected chains, once launched can be sent back and forth to other multi-currency capable networks (currently other independent PBaaS chains and Ethereum as ERC20s). (edited)

-Currencies on Verus can also be defined as "mapped currencies", which map 1:1 to an existing currency on Ethereum (eg. DAI), and can then be sent from Ethereum with simple transactions and received and used as the new "mapped currency", or sent back to Ethereum and used there as the original currency. For example, I could make a currency called MyBucks and map it to DAI. It will always be provably mapped and convertible 1:1 to and from DAI by sending it to and from Verus to Ethereum.


- Currency launches can raise funds in 3 ways. Each of these fundraising options creates a currency that is not 100% backed, and has a price that responds to market forces. 100% backed currencies do not change their relative price to the underlying basket reserve when they are converted to or from reserves. Fractionally backed currencies, which result from fundraising or endowing launch grants/pre-allocations to DAOs or entities such as foundations, whether time-locked or not, take their funding from a percentage of the reserve backing. Except in the case of a new blockchain launch, which creates new native currency for operating the proof of stake of the blockchain, any currency that uses fundraising options will be a fractionally backed currency which will appreciate when more people convert to it and depreciate when more convert from it. If a launch is refunded due to minimum participation options that are not met, no fundraising is received: (edited)

- Pre-launch discount - all participants contributing to the launch before it goes live on its start block get a discount to the initial on-chain price of the currency. This is usually accompanied by a maximum cap on pre-conversion participation to ensure that the currency would still be in demand when it goes live.

- Pre-launch carve-out - this enables a percentage of each of the initial participation currencies to be carved out of the launch and total reserve ratio in a price-neutral manner and sent directly to the launching identity upon successful launch.

- Pre-allocation - this enables some of the newly launched currency to be pre-allocated to one or more identities. If the currency is fractional, this happens in a price-neutral manner, and again is subtracted from the reserve ratio. Recipients can optionally be time-locked IDs for vesting or unlock periods.

Testnet Reset
To reset your testnet make sure Verus is closed (and no testnet daemon running) and delete the following directories, then restart the testnet daemon (or relaunch Verus Desktop, deactivate verustest and re-add verustest native):
Linux: ~/.Komodo/vrsctest, ~/.verustest
Mac OS: ~/Library/Application Support/Komodo/vrsctest, ~/Library/Application\ Support/VerusTest
Windows 10: %AppData%\Roaming\Komodo\vrsctest\, %AppData%\Roaming\VerusTest or %AppData%\Komodo\vrsctest\, %AppData%\Roaming\VerusTest
CLI: https://github.com/VerusCoin/VerusCoin/releases/tag/v0.9.1
GUI: https://github.com/VerusCoin/Verus-Desktop/releases/tag/v0.9.1

Ethereum's network traffic has exposed developers to new challenges with the biggest being speed and transaction fees. These problems are hectic but might introduce a premature and permanent solution to this adversity before it could get too late or complex to solve. It seems to be a good exposure as blockchains are yet to become the standard financial structure for society.

The bigger the network gets the more congestion it faces, slowing down the speed of the network. Blockchains are adopting different measures to avoid this such as Layer-2 platforms, Rollups, sidechains, newer block generating techniques, etc. However, a delegation of any sort can bring security risks so there is a new technique introduced called sharding.

What is Sharding

Sharding is a blockchain distribution method that basically distributes the blockchains into smaller fragments of blockchain so that one single block doesn't have to distribute the entire network load. This means that any pending transactions do not have to wait for the next block in order to be finalized.

How does Sharding work?

Sharding would allow a blockchain to distribute data into multiple but native blockchains that will not compromise the scalability, security, and decentralization of a blockchain. Every shard/node here will have to keep a small portion of the block instead of a full ledger.

In some cases, the nodes might only keep snapshots or proof of data instead of the actual data. These shards would be interconnected and faster with more periodic data to record. The selection of validators to verify the shard is random and sequential so every validator would get a chance and be incentivized when needed.

This solution is overall effective, fast, stable, and secure as compared to other scaling solutions out there. Even though in its early adoption phases many popular blockchains have modified sharding methods to befit their needs.

Ethereum 2.0 is said to adopt 64 shards with each shard having 100 validators, overall making the network exploit extremely difficult. The near protocol is also adopting sharding techniques in order to scale their blockchain and neglect the use of side-chains or delegated blockchain distribution.

NEW dAPP VERSION RELEASED!
Hi @everyone

This is a minor, but very important release, of the Tokel dApp. It includes lots of bug fixes that the community raised and helped us track down:
- nSPV/network connection should work better now, with less timeouts. Let us know!
- IPFS media for tokens and NFTs should always load now (provided there’s someone broadcasting the file), even if your local IPFS node doesn’t work, as we added a gateway fallback
- Some wallets containing lots of miner inputs were having problems to login. This should be fixed now.
-The fee estimation for token creation in the dApp now accounts for the marker fee as well
-The huge transaction values you see on your activity are fixed now (sorry, I guess?)
-Some typos were found and fixed
-If you create a token with no collection or number, we'll now omit this data from being written the blockchain instead of writing empty fields
- TKLTEST is gone! Selecting TKLTEST as your network will now default to TKLTEST2 (where we’re testing new exciting stuff)

Thanks to all community members for engaging in raising issues and helping us track them down. We're busy working on new features behind the scenes, but please do let us know of any new shiny bugs for us to hunt.

Also, this is another reminder that full nodes must update their codebase from the Tokel Github repo ASAP. There are currently about 15 nodes that have not been updated and need to.

You can take a look at known bugs here: https://github.com/TokelPlatform/tokel_dapp/issues?q=is%3Aissue+is%3Aopen+label%3Abug

Grab the newest release 1.2.1 here https://github.com/TokelPlatform/tokel_dapp/releases/tag/v1.2.1

There are some prerequisites for you to better understand blocks. These prerequisites are terms you frequently come across when you hear about Blockchain and you will see them throughout this article.

What is a Blockchain?

Blockchain is a digital distributed ledger or database of transaction records that consist of immutable data in a chain form with each record set known as a BLOCK followed by another block. These blocks are immutable and any changes will follow up and change the entire blockchain set since they follow each other.

Hashing

Hashing is a one-way cryptographic formula to check the validity of any input (Strings, chars, etc) and convert it into a hash-value which is irreversible and cannot be converted back to the original input.

In a blockchain, each block is encoded by a hash which is a fixed output problem that is being solved by multiple nodes (Computers), and upon correctly guessing the solution the network creates a new block and moves any pending transactions from the older block to the newer block.

This is a one way function, to ensure security the hash can never be converted back to the original input

The system rewards the node that made the correct guesses in form of a block reward. More specifically, the system creates a mathematical problem and you (node) need to guess the solution to generate a new block for the blockchain and earn the reward for the solution.

Of course, this is all done by your computer and the more powerful the machine the more guesses it will make per second (hash rate) increasing the chances of making a correct guess.

Network Consensus

The mechanism that is used for a decentralized network or blockchain is to maintain trust. security and finality between nodes or distribution of the network is called a Network consensus or Blockchain consensus.

This mechanism is unique throughout the blockchain and all parties involved within the system agree upon this method to make any operation in the blockchain.

What is a Block?

Block is a data structure in a blockchain database that usually store data, transaction hash, and the hash of the previous blocks to create a chain of blocks. In some special blockchains, it can also store special data types, i.e supply chain blockchains or gaming blockchains.

Blocks work as homogenous data structures depending on the type of blockchain protocol. I.E, Bitcoin block stores the data of sender, receiver, and amount with a transaction hash of the current and previous block.

These blocks are immutable to ensure safety and any kind of changes made in these blocks will affect the entire blockchain, this is possible due to the correlation between blocks. The block hash algorithm is almost impossible to guess and take over the network.

Each of the newer blocks contains the record from the previous block

Why do we need blocks?

Just like building blocks, they are the foundation and the very thing that make up a blockchain. There is always a limit to the storage capacity of a block which demands newer blocks for a network to reduce congestion and ensure that there is an incentive and interest for nodes involved with the blockchain.

Generating newer Blocks also means multiple parties are invited to the network so which ensures the network is really distributed and decentralized as multiple nodes are being connected to the network removing any single central authority.

How are blocks generated?

You might have often heard about making money by mining or minting, to simplify, this is the part where people are getting paid, basically for creating new blocks.

Different protocols have different network consensus which results in different techniques to create a new block. There are two main consensus mechanisms as of today with many modified but subordinate versions:

Proof Of Work

In this model, blocks are generated by working for the network and solving the hashes using heavy machines or mining equipment (ASIC machines). The block is distributed and everyone can get involved and try to solve the hash.

A proof of work model encourages miners to compete with each other to guess the correct block hash first. A lot of computation power and energy is needed to mine coins and generate new blocks to make sure a POW blockchain is online and secure.

Proof of Stake

Proof of stake consensus is contrary, less-hectic and a bit unfair type of network consensus. In a proof of stake consensus, the validators (miners in POW) are chosen at random and only one out of many validators are chosen to create a new block and get rewarded.

These validators stake huge amounts of coins which are locked away as long as they are validating the network, this creates a monopoly for validators with bigger shares in the network.

This system is more eco-friendly and scalable in a way as it randomly chooses from a fixed number of validators to create a new block and mint rewards that are validated by all the validator nodes present in the systems. Geavy hardware and power consumption is redundant.

The easiest way to make money with AtomicDEX is by market-making for different assets. Providing liquidity invites risks one of such is impartial losses, however, there is one way to make risk-free profits by market-making for stable coin pairs in AtomicDEX.

AtomicDex recently took it on another level and integrated 13 new blockchains in the last application update to v 0.5.4 Beta. Adex users can now store, send, receive and trade these coins and their tokens within AtomicDex.

This exposes users to more stable coin trading pairs as tons of different stable coins come in to play with these blockchains, some are native while most are pegged versions of stable coins from other blockchains.

atomicdex new protocols
Stay tuned on the socials to get notified of the giveaways and competitions held by the AtomicDEX team!

Different protocols have their own versions of stable coins, mostly protocols that are EVM capable, and use pegged tokens to bridge tokens from other blockchains as their own in their native blockchain.

These tokens will use the primary coin of their respective blockchains for a gas fee such as BNB for BUSD on the Binance smart chain, or Ethereum if it is BUSD-ERC-20 the Ethereum version of the Binance USD stable coin.

Market Making for Stable Coins without Loss?

Making Zero Risk Profit with AtomicDEX
This is the DEX Page of the AtomicDEX Desktop Application

That is all needed to make money with AtomicDEX, the profit ratio is lesser but tamed for day traders, or enthusiast.

Experience Crypto
© 2021 komodefi.com. Powered by Komodefi