To begin this tutorial you should have a project that mirrors this git repo.
At this point we have a smart contract and some interactions, but none of it is on the blockchain. A lot of the Dev Server and API work was to give you a ground level introduction to working with a blockchain and I hope you now have that understanding.
This next set of tutorials will have us uploading our smart contract to Lamden’s TestNet and applying what we have learned about interacting with the smart contract to change our frontend to work with the Lamden TestNet. …
The token swap will begin on September 16th, 2020 at 4pm UTC, the day of the Lamden Mainnet release.
You can view a mainnet countdown timer at lamden.io.
We have had a lot of questions about the token swap recently so lets address them all.
The current circulation of TAU tokens are Ethereum based tokens called ERC20 tokens. The swap process allows you to turn your Ethereum ERC20 TAU into Lamden TAU.
Lamden TAU is used to pay for transactions on the Lamden blockchain.
As stated above the token swap will not be active till the official Mainnet release which is September 16th, 2020 at 4pm UTC. …
I ranted on twitter the other day about HTTPS being annoying
I got my answer so why not write about it!
Basically my assumptions that Netlify would handle the HTTPS for me was incorrect even though their website lead me to believe it would, but that’s besides the point.
The only Netlify config needed was to point the subdomain to the Digital Ocean Droplet IP address in the DNS settings.
Netlify just happens to host my DNS record. You add the same exact record on whoever hosts your DNS. “A Records” are a DNS standard and point a DNS name to an IP address. …
…this is a continuation from A Frontend for your Smart Contract : A
Our smart contract doesn’t just store balances. It also gives our users the ability to send tokens to other users by calling the “transfer” method.
In Part 2 we created an API endpoint to be able to call this transfer method and provide the arguments.
What we need now is a form on our website that lets the user fill in the required arguments (receiver and amount). And then we need to feed that information to the API.
This tutorial is part of a series that demonstrates how to create a working application with Python contracting.
In previous tutorials we created a Python smart contract as well as an API dev server to interact with it.
Here are the previous two tutorials in this my_token series
In this tutorial (Part 3a) we will install a frontend web framework called Sapper to create a user interface for our smart contract.
For this test we will use a simple lightweight framework called Sapper.
You will need the dependencies from the last two tutorials as well as these two new ones. …
Full stack developers are used to developing both the backend and frontend in tandem. The problem with using blockchain as a backend is, they are generally complicated to setup and even more complicated to interact with. This slows down what should be a simple interaction between storage and user interaction.
A dApp (Decentralized Application) is an application that interacts with a blockchain. The most common these days is a web app with these basic interactions:
During development it would be nice to streamline this process so that I didn’t have to wait for the blockchain to process my transactions every time. I just want to get some state to render a route so I can mess with layout. I also want to design my user interactions with the blockchain across different routes without mocking data. …
Love Python? Interested in blockchain? Curious about smart contracts? Do you just like to learn cool stuff?
Then I made this tutorial for YOU!
After this tutorial you will understand:
For this tutorial we will be using a Python contracting package created by Lamden.
But before we get to that, as always, we need to install dependencies, but just one.
Want to read this story later? Save it in Journal.
The contracting package will require mongo db to store the state of our contract. …
After a long development cycle Lamden has launched its blockchain protocol. This network is dubbed “RC Net”.
Let’s start by answering some frequently asked questions:
RC stands for “Release Candidate”. In development terms an RC is a precursor to the final product.
RC Net currently runs on 4 Lamden AWS Nodes (2 Delegates and 2 Masternodes) and 3 community run Delegate nodes.
The core functionality exists for transaction and smart contracting on RC Net. What doesn’t exist are our tools which will allow developers to begin creating python smart contracts.
The wallet requires an update to query balances and send transactions on RC Net, the smart contracting IDE is only in alpha status and the block explorer is in early stage development. These tools will be released shortly but are waiting on core updates to RC Net. …
Are you a Developer or do you know a developer? Here’s a chance to earn TAU by helping our team secure our testnet.
We announced the launch of our early testnet (dubbed “AnarchyNet”), at the end of December 2018. Since then we have had an overwhelming response from the community. People have been claiming wallets and sending AnarchyNet’s native token, “Dark TAU”, around to each other.
Well, they were anyway. Right up until AnarchyNet lived up to its name and mysteriously went down. A few members of the community thought they crashed it but attempts to reproduce their steps did not recreate the crash. …
Smart contracts are poised to usher in a new era of peer-to-peer transactions and activities. Many things have been written about smart contracts and their “trust-less” nature but how easy is it to validate any smart contract does what its author claims it does?
In a decentralized setting trust is earned, not assumed. So then as a developer, customer or business attempting to interact with smart contracts, how do you begin to trust anything?
Ethereum’s smart contract language ‘Solidity’ is the major player in the space, and adopted as the smart contract language of choice by other platforms. …