submitted by alexngn201 to Tomochain [link] [comments]
Hi everyone. Pleased to be here! Thank you for taking your time to join me.
I’m the Chief Business Development Officer for TomoChain.
Educationally I graduated university with degrees in both Industrial Engineering and Economics from Georgia Tech, and later earned an MBA from the Wharton School of Business.
I grew up as a gaming addict and have a video game collection that is a bit unwieldy. Dozens of consoles and, at one point, over 13 classic arcade machines.
So, before crypto, I spent much of my profession in the gaming space. I was a Game Designer, Game Producer, and eventually Studio Head for a major games studio that was recently purchased by Rockstar Games. I have run my own game-related tech businesses as well.
I fell into crypto back in 2014, and over time it became a second passion of mine as I began to truly understand the value of decentralization. True ownership of data was not possible until Bitcoin came along and that is simply a powerful and game-changing message to a world structure built on an opposing foundation.
TomoChain is a Public Blockchain powered by Proof-of-Stake Voting. TomoChain launched into Mainnet 1 year ago in December 2018. It is secured by 150 Masternodes, of which I’m proud to be an operator myself. TomoChain is EVM Compatible and runs at a speedy 2000 TPS with a 2 Sec Blocktime. Gas fees are almost zero too.
Based out of Vietnam, TomoChain is Southeast Asia’s largest public blockchain. We are focusing on developing a full suite of DeFi products. We also have commercial and enterprise clients. TomoChain has a number of major crypto-partnerships including notables like Neo Blockchain, Chainlink and Crypto.com. Our Masternode network is run by some of the most recognizable players in the space as well, including Neo Global Capital, CoinGecko, HashQuark, KuCoin, and more large players are on the way.
TomoChain earned its place onto Binance.com with a fee-free listing last year by winning the BinanceDEX community vote in August 2019. Binance has written us up in a detailed Binance Research Report and awarded us the V-Label. We have also been in a number of their reports, including those related to Dapps and DeFi. We have been interviewed by Forbes.com official and had an in-person interview at NASDAQ, in the heart of Times Square, about TomoChain and our upcoming TomoX Protocol.
In China, specifically, we have been integrated into and have solid relationships with various blockchain players including HashQuark, HashKey, CoboWallet, Conflux, and many others. We launched an Ecosystem Development partnership with Neo Blockchain last December and co-hosted a meetup + workshop with them as well.
GEARED FOR REAL WORLD USE
Now, let’s talk about how TomoChain has been built for real-world use.
We’re looking at Payments & DeFi as low hanging fruit when it comes to user adoption and TomoChain is developing a suite of tools to support this. The biggest challenge for having users benefit from Blockchain on a day-to-day basis is how much friction is involved to acquire, store and use it. Even stable coins are dual currency systems. The Stablecoin and then the Native Token to pay gas fees. Blockchain is simply not user-friendly.
Our view is that the true solution for Blockchain adoption by the world is end-users shouldn’t need to know they are using blockchain technology at all. It should be a hidden technology layer, similar to payment processor settlements or even the internet distribution centers/routers that power this very AMA we’re all participating in right now. Do we need to know the underlying technology infrastructure to use them? Nope.
We are developing a system to hide this friction, so the TomoChain blockchain can be integrated into real-world applications that you use every day on mobile or web.
There are 3 protocols that we are building to enable this future: (1) TomoZ: Zero Friction (2) TomoX: The DEX Protocol (3) TomoP: The Privacy Suite.
TomoZ: Zero Friction - Our TomoZ protocol is a core starting point to the solution for mass market use of blockchain technology. TomoZ: Zero Friction allows for token issuance and use by having gas fees paid by the token itself. That means you don’t need TOMO to send transactions. You don’t even need to know you’re using the TomoChain blockchain.
So you could buy a cup of coffee at a café using loyalty points that are TomoZ tokens. The customers redeem for their coffee or earn it, but they don’t even have to know it’s a blockchain token which they actually own.
This approach is structured to enable the next million-plus users to utilize blockchain as a technology layer. After all, the real value of any Blockchain is in its utilization of high-quality transactions.
Now, TomoZ transactions aren’t FREE. It actually does use TOMO, but that’s hidden from the end-user. The way it works is that the token issuer deposits a small amount of TOMO into a pool. Every time the token is sent, TOMO is taken from this pool to pay the Masternodes.
The key is that the end-user doesn’t need to get involved with internal workings, which is why we call it the Zero Friction protocol
Now let’s talk about TomoX: The DEX Protocol
TomoX is an upcoming DEX Protocol that allows anyone to launch their on permissionless Decentralized Exchange in minutes. It requires very little technical knowledge making it a near turn-key solution.
TomoX is the fastest DEX experience since it’s a Layer 1 protocol. This means it’s run and secured by the entire TomoChain network. Our Masternodes manage the DEX instructions directly, rather than other DEXs that operate as a Layer 2 protocol. What this means is TomoX DEXs will operate at about 50x faster than a typical 0x exchange. That significantly improves the end-user experience.
TomoX DEX operators have access to a shared liquidity pool across all DEXs. That means a user buying on one DEX can be matched with a user selling on another DEX. Of course, Operators can customize and choose which tokens to include.
TomoX is fully decentralized since the Order Book is on-chain. Many other semi-decentralized exchanges store the OB on a centralized service in order to speed up the execution. That means there is a centralized point of weakness for them. TomoX minimizes custody and security challenges that centralized exchanges have too since all users are always in possession of their assets.
TomoX is currently in testnet and you can checkout TomoChain’s own DEX, aptly called TomoDEX, here: https://dex.testnet.tomochain.com/
Here is a link to get some free Testnet TOMO that can be used on the testnet version of TomoDEX: https://faucet.testnet.tomochain.com/
And finally, there is TomoP: Privacy Suite - TomoP is currently in testnet and is going to be the FASTEST way to send tokens privately. 2-4 seconds fast!
Any token issued on TomoChain will be able to utilize TomoP to send privately and anonymously. And that’s not all. We are including access to wrapped BTC, ETH, USDT, and other tokens that can also utilize the blazing speed and privacy that TomoP will offer.
Dapp privacy is a major part of TomoP. It is going to allow for the creation of Dapps to be built to handle customer data with true privacy, including from the Dapp operators themselves. This can jumpstart a new wave of applications geared towards hiding user information, transactions, assets owned, etc.
We are issuing a new token standard (TRC21p) which will be purely private. The only data available will be on its token supply. Token issuers can optionally provide auditing access to enforcement authorities to meet regulatory compliance. What this means is if the next Global PayPal/Skrill/Alipay competitor can build their service right on TomoChain and meet the most basic criteria required to stay above board in many jurisdictions.
If you guys want to check TomoP on testnet go here and login: https://wallet.testnet.tomochain.com/
Get some free Testnet TOMO that can be used with the TomoP testnet: https://faucet.testnet.tomochain.com/
Questions from the host
1. It’s been stated that TomoChain was on track to be a cash flow positive business, is it currently cash flow positive? What services or products is it offering to bring in this revenue?
Yes, absolutely. Our plan is to be cash flow positive this year. This really goes back to the level of experience our executive team has. Everyone is seasoned, having come from different fields, in big business and startups. Before the crazy boom of ICOs and IEOs, raising funding for traditional startups required considerable proof that there was market fit, that there were actual customers to drive revenue, and a model for growth.
We knew that TomoChain’s funds raised during the ICO were for a space that has yet to prove itself so the company had to be smart in budgeting for an uncertain future. And part of that initial preparation was selling much of the ICO proceeds into fiat. Something MANY blockchain startups did not do, largely due to ambitious teams that are also headed by very inexperienced leaders. So while the bubble burst, we had capital to continue operations and to even scale it.
And, we ARE running a business. A sustainable business requires us to identifying areas to generate income in order to minimize risk and to sustain the business in the long term. So we do both consulting and services work by helping clients to develop wallets, launch tokens (Orbyt), build exchanges (AIS), and of course enterprise solutions on the blockchain of which we have clients based out of Japan and in the Middle East using blockchain for traceability solutions across various industries from automotive, healthcare, and food.
2. What is the most strategical step TOMO is doing to bring adoption of TOMO coin to our daily lives?
Empowering businesses with a truly scalable blockchain that can be used by thousands and millions of users. We see user adoption of blockchain coming from businesses that base their solutions on blockchain technology. And, TomoChain has a number of real income-generating companies that have built on us, from exchanges to payment services to enterprise clients. Not bad for 1 year I say, especially during a stagnant market. Here are some examples.
UcarPac – A Top 10 User Car company in Japan is building traceability solutions on the blockchain. We completed a POC at the end of last year. After the assessment, the client decided it was solid and commissioned Phase 2 to expand the development of the project for commercialization purposes
Triip Protocol – Triip is a destination service for travelers to book vacations powered by Blockchain. Triip is a Shark Tank Vietnam alumnus, and the first ICO on TomoChain. Users can book tours and staycations using Triip or TOMO tokens.
WisePass – A service that sells subscription services to get discounted Starbucks, Singha Beer, and even makeup (of all things) integrated TomoChain as a payment solution
“Undisclosed Vendor” – Soon to be announced, a large player in the corporate gift giving business is also launching a Dapp on TomoChain to allow for them to make purchases with TOMO across thousands of items.
Maka - A peer-to-peer marketplace to conveniently buy/sell TOMO and other blockchain tokens using standard payment gateways, including e-wallets and bank transfers.
Coin98 – A local Vietnam crypto media company launched an App to allow for their community to earn their TomoChain token called C98 and use it for products and services geared around investors and gamers. The reception has been HUGE. 95,000 users and generating 500K+ transactions on our blockchain within 3 months of their launch! They are proving that innovative new business models can be adopted relying on and being blockchain specific.
3. Do you have any plans to collaborate with developers or attract more Dapps built on TomoChain?
We are today. Our founders run the largest Blockchain Developer community in Vietnam and we work with a number of them to help develop solutions on the blockchain.
Our team has held Hackathons a few times over the last couple years and we have done developer workshops too, including one with Neo Blockchain. And this year we are working closely with educational institutions to launch blockchain courses in Vietnam.
Every Dapp developer we work with is a partner. We try to provide as much support as possible, both technical and marketing. A number of Dapps are games on TomoChain and we hold contests regularly to promote the developers and their titles.
Since we are focusing on alleviating the friction of blockchain technology, we are building out an API that will make it even easier for developers to integrate blockchain into standard applications. This is intended to allow standard non-blockchain application developers to operate in an environment they are accustomed to while also having the benefit of blockchain technology accessible.
Onboarding more developers will take time. However, I’m confident we’re on the cusp of something wonderful in the coming years that will change the relationship between users and applications enabled by blockchain. Entirely new economic structures can be set up since it’ll be the users owning all of their data for the first time in digital history. And true ownership is a powerful motivator that can be harnessed by innovative blockchain businesses.
Yes. You pick a peer and after some setup, create a bitcoin transaction to fund the lightning channel; it’ll then take another transaction to close it and release your funds. You and your peer always hold a bitcoin transaction to get your funds whenever you want: just broadcast to the blockchain like normal. In other words, you and your peer create a shared account, and then use Lightning to securely negotiate who gets how much from that shared account, without waiting for the bitcoin blockchain.
Yes, Lightning is open source. Anyone can review the code (in the same way as the bitcoin code)
Similar to the bitcoin network, no one will ever own or control the Lightning Network. The code is open source and free for anyone to download and review. Anyone can run a node and be part of the network.
No, your bitcoin will never leave the blockchain. Instead your bitcoin will be held in a multi-signature address as long as your channel stays open. When the channel is closed; the final transaction will be added to the blockchain. “Off-chain” is not a perfect term, but it is used due to the fact that the transfer of ownership is no longer reflected on the blockchain until the channel is closed.
Example: A and B have a channel. 1 BTC each. A sends B 0.5 BTC. B sends back 0.25 BTC. Balance should be A = 0.75, B = 1.25. If A gets disconnected, B can publish the first Tx where the balance was A = 0.5 and B = 1.5. If the node B does in fact attempt to cheat by publishing an old state (such as the A=0.5 and B=1.5 state), this cheat can then be detected on-chain and used to steal the cheaters funds, i.e., A can see the closing transaction, notice it's an old one and grab all funds in the channel (A=2, B=0). The time that A has in order to react to the cheating counterparty is given by the CheckLockTimeVerify (CLTV) in the cheating transaction, which is adjustable. So if A foresees that it'll be able to check in about once every 24 hours it'll require that the CLTV is at least that large, if it's once a week then that's fine too. You definitely do not need to be online and watching the chain 24/7, just make sure to check in once in a while before the CLTV expires. Alternatively you can outsource the watch duties, in order to keep the CLTV timeouts low. This can be achieved both with trusted third parties or untrusted ones (watchtowers). In the case of a unilateral close, e.g., you just go offline and never come back, the other endpoint will have to wait for that timeout to expire to get its funds back. So peers might not accept channels with extremely high CLTV timeouts. -- Source
Tiny payments are possible: since fees are proportional to the payment amount, you can pay a fraction of a cent; accounting is even done in thousandths of a satoshi. Payments are settled instantly: the money is sent in the time it takes to cross the network to your destination and back, typically a fraction of a second.
Yes, but not in theory. You could make a poorer lightning network without it, which has higher risks when establishing channels (you might have to wait a month if things go wrong!), has limited channel lifetime, longer minimum payment expiry times on each hop, is less efficient and has less robust outsourcing. The entire spec as written today assumes segregated witness, as it solves all these problems.
No, for now. For the first version of the protocol, if you wanted to send a normal bitcoin transaction using your channel, you have to close it, send the funds, then reopen the channel (3 transactions). In future versions, you and your peer would agree to spend out of your lightning channel funds just like a normal bitcoin payment, allowing you to use your lightning wallet like a normal bitcoin wallet.
Not really. Anyone can set up a node, and so it’s a race to the bottom on fees. In practice, we may see the network use a nominal fee and not change very much, which only provides an incremental incentive to route on a node you’re going to use yourself, and not enough to run one merely for fees. Having clients use criteria other than fees (e.g. randomness, diversity) in route selection will also help this.
Lightning is already being tested on the Mainnet Twitter Link but as for a specific date, Jameson Lopp says it best
Nope, because there is no custody ever involved. It's just like forwarding packets. -- Source
Furthermore, the Lightning Network scales not with the transaction throughput of the underlying blockchain, but with modern data processing and latency limits - payments can be made nearly as quickly as packets can be sent. -- Source
Each exchange will get to decide and need to implement the software into their system, but some ideas have been outlined here: Google Doc - Lightning Exchanges
Note that by virtue of the usual benefits of cost-less, instantaneous transactions, lightning will make arbitrage between exchanges much more efficient and thus lead to consistent pricing across exchange that adopt it. -- Source
According to Rusty's calculations we should be able to store 1 million nodes in about 100 MB, so that should work even for mobile phones. Beyond that we have some proposals ready to lighten the load on endpoints, but we'll cross that bridge when we get there. -- Source
No you'd remember the information from the last time you started the app and only sync the differences. This is not yet implemented, but it shouldn't be too hard to get a preliminary protocol working if that turns out to be a problem. -- Source
Lightning is based on participants in the network running lightning node software that enables them to interact with other nodes. This does not require being a full bitcoin node, but you will have to run "lnd", "eclair", or one of the other node softwares listed above.
All lightning wallets have node software integrated into them, because that is necessary to create payment channels and conduct payments on the network, but you can also intentionally run lnd or similar for public benefit - e.g. you can hold open payment channels or channels with higher volume, than you need for your own transactions. You would be compensated in modest fees by those who transact across your node with multi-hop payments. -- Source
Sure, you can help write up educational material. You can learn and read more about the tech at http://dev.lightning.community/resources. You can test the various desktop and mobile apps out there (Lightning Desktop, Zap, Eclair apps). -- Source
No -- Source
lit doesn't depend on having your own full node -- it automatically connects to full nodes on the network. -- Source
LND uses a light client mode, so it doesn't require a full node. The name of the light client it uses is called neutrino
Upon opening a channel, the two endpoints first agree on a reserve value, below which the channel balance may not drop. This is to make sure that both endpoints always have some skin in the game as rustyreddit puts it :-)
For a cheat to become worth it, the opponent has to be absolutely sure that you cannot retaliate against him during the timeout. So he has to make sure you never ever get network connectivity during that time. Having someone else also watching for channel closures and notifying you, or releasing a canned retaliation, makes this even harder for the attacker. This is because if he misjudged you being truly offline you can retaliate by grabbing all of its funds. Spotty connections, DDoS, and similar will not provide the attacker the necessary guarantees to make cheating worthwhile. Any form of uncertainty about your online status acts as a deterrent to the other endpoint. -- Source
You typically want to have more than one channel open at any given time for redundancy's sake. And we imagine open and close will probably be automated for the most part. In fact we already have a feature in LND called autopilot that can automatically open channels for a user.
Frequency will depend whether the funds are needed on-chain or more useful on LN. -- Source
You don't really set up a "node" in the sense that anyone with more than one channel can automatically be a node and route payments. Fees on LN can be set by the node, and can change dynamically on the network. -- Source
Yes but it has to be implemented in the Lightning software being used. -- Source
You won't have to do anything. With autopilot enabled, it'll automatically open and close channels based on the availability of the network. -- Source
I have been eager to try LN mainnet since the very beginning of it. I've found out about lnd, eclair, zap and other wallets but every scenario I tried to use it failed because of critical issues:submitted by pabou to Bitcoin [link] [comments]
Setting up Pi is easy, lots of tutorials over the internet, not gonna discuss it here. Then I had to obtain bitcoind (current rel: bitcoin-0.17.0-arm-linux-gnueabihf.tar.gz) and lnd (lnd-linux-armv7-v0.5-beta.tar.gz), create a bitcoin technical user, deploy the tools, configure and install new systemd services and go through the configs. This is a tricky part, so let's share:
# Generated by https://jlopp.github.io/bitcoin-core-config-generato # This config should be placed in following path: # ~/.bitcoin/bitcoin.conf # [core] # Set database cache size in megabytes; machines sync faster with a larger cache. Recommend setting as high as possible based upon machine's available RAM. dbcache=100 # Keep at mostWhooaa, this online config generator is really helpful, but I still had to manually correct a few things. The last line is obviously generated by rpcauth.py, I disabled the wallet functionality as lnd is going to take care of my funds. ZMQ is not available to the network so only my LND can use it, RPC usage I still have to think through a little, in general I would like to have my own block explorer some day but also be safe from any hacking attempts (thus I would need at least 2 RPC ports/user accounts - one for lnd, one for block explorer frontend). No ports open on firewall at this time, only UPnP is active and gently opens 8333 for block/tx transfers.
Now, synchronizing the blockchain took me time from mid-July to early September... The hard drive is really slow, also my external HDD drive has some trouble with its A/C adapter so Pi was getting undervoltage alerts all the time. Luckily, it is just downclocking when it happens and slowly but steadily synchronized the whole history. After all, I'm not paying even $5 monthly for a VPS, it is by design the cheapest hardware I could use to set up my LN wallet.
When bitcoind was ready (I've heard some stories about btcd but I don't trust this software yet, sorry), it's time to configure lnd.conf:
[Application Options] debuglevel=trace rpclisten=0.0.0.0:10009 externalip=X.X.X.X:9735 listen=0.0.0.0:9735 alias=X color=#XXXXXX [Bitcoin] bitcoin.active=1 bitcoin.mainnet=1 bitcoin.node=bitcoind [Bitcoind] bitcoind.rpchost=127.0.0.1 bitcoind.rpcuser=X bitcoind.rpcpass=X bitcoind.zmqpubrawblock=tcp://127.0.0.1:28332 bitcoind.zmqpubrawtx=tcp://127.0.0.1:28333Here I've had to XXX a little more fields, as not only the bitcoind RPC credentials are stored here, but also my node's public information (it should be illegal to run nodes without specifically selected color and alias!). It is public (and I had to open port 9735 on my firewall), but not necessarily connected to my reddit account for most of the adversaries, so let's keep it this way. In fact, I also see a security vulnerability here: my whole node's stability depends on the IP being static. I could swap it for a .tk domain but who can tell if the bad guys won't actively fight DNS system in order to prevent global economic revolution? As such, I would rather see node identification in LN based on a public key only with possible *hints* of last-known-ip-address but the whole discovery should be performed by the nodes themself in a p2p manner, obviously preventing malicious actors from poisoning the network in some way. For now, I consider the IP stability a weak link and will probably have to pay extra Bitcoin TX fees when something happens to it (not much of a cost luckily!).
Okay then, lnd is up and running, had to create a wallet and give it a night for getting up to speed. I don't know really what took it so long, I'm not using Windows nor 'localhost' in the config so the issues like #1027 are not the case. But there are others like #1545 still open so I'm not going to ponder much on this. I haven't really got any idea how to automatically unlock the wallet after Pi restart (could happen any time!), especially since I only tried to unlock it locally with lncli (why would I enter the password anywhere outside that host?), but let's say that my wallet will only be as stable as my cheap hardware. That's okay for the beta phase.
Finally, zap-desktop required me to copy tls.cert and admin.macaroon files to my desktop. If my understanding of macaroon (it's like an authentication cookie, that can later be revoked) is correct then it's not an issue, however it would be nice to have a "$50 daily limit" macaroon file in the future too, just to avoid any big issues when my client machine gets stolen. Thanks to this, I can ignore the silly cloud-based modes and have fully-secure environment of my home network being the only link from me to my money.
Aaand there it is. The IP took some time to advertise, I use 1ml.com to see if my node is there. The zap interface (ZapDesktop-linux-amd64-v0.2.2-beta.deb) lacks lots of useful information so I keep learning lncli syntax to get more data about my new peers or the routes offered. The transactions indeed run fast and are ridiculously cheap. I would really love to run Eclair with the same settings but it doesn't seem to support custom lnd (why?). In fact, since all I need is really a lncli wrapper, maybe it will be easy to write my own (seen some web gui which weighs 700MB after downloading all dependencies with npm - SICK!). Zap for iOS alpha test registration is DOWN so I couldn't try it (and I'm not sure if it allows custom lnd selection), Zap for Android doesn't even exist yet... I made a few demo transactions and now I will explore all those fancy t-shirt stores as long as the prices are still in "early investor" mode - I remember times when one could get 0.001 BTC from a faucet...
If you find any of the facts presented by me false, I am happy to find out more in the discussion. However what I did I did mostly for fun, without paying much attention to the source code, documentation and endless issue lists on github. By no means I claim this tutorial will work for you but I do think I shared the key points and effort estimations to help others decide if they want a full-node LN client too. I'm also interested in some ideas on what to do with it next (rather unlikely that I will share my lnd admin.macaroon with anyone!) especially if it gives me free money. For example, I can open 1000 channels and start earning money from fees, although I no longer have more Bitcoins than the LN capacity yields... I will probably keep updating the software on my Pi until it leaves beta phases and only then will pour more money inside. I'm also keen on improving the general security of my rig and those comments I will answer more seriously.
Maximum Token Supply: 183,744,990
14.8 For sane instructions, please refer to https://github.com/eruina/laffka, most relevant technical stuff is in README.md - https://github.com/eruina/laffka/blob/masteREADME.mdsubmitted by faceless-valhalla to darknet [link] [comments]
14.8 RELEASE 2.01
pip3 -r requirements.txt
10.8 Made one test sale, spores for for microscopy in syringe.
Can confirm, payment of mailing expenses made to my wallet rapidly and without problems.
Revamped site, welcome: http://laffka6wwduoexvb.onion/
source code will be availible 12.8
9.8 Items can be added, removed and edited from console panel:
And this is how it looks like listed: http://laffka6wwduoexvb.onion/item/6
Custom list of amounts to ship is in use now, howver - admin console validates only if session authorized.
What does this mean? Means that putting wrong values into database might bring whole Laffka down. Especially amount lists and orders which include both MainNet and TestNet orders.
Temporary solution would be to implement /rescue page, where admin can delete any offending row from database. Bit lame, but would do for now.
I am also puzzled at in which form package is to make. Well, have 3 days to figure it out.
8.8 At very basic level Laffka works in very basic level without any external stuff. Here:
Second part of admin console
At the risk of being labeled pedlling crap - shop example on laffka should work: http://sporeikzj77hnrxq.onion/ (yes, it is fully working little shop)
8.8 Items can be changed from console now. One can change, but not add or remove items at the moment.
Ugly as hell, but admin console in fact doesnt need to be pretty.
it needs to be functional.
6.8 Orders part of console is finished. Orders shown - ones that are paid, and ones that are marked with note.
Rather nifty, but probably requires additional changes after code is released.
Order 98 will be shown even if Wif key is swept. Order 99 will disappear after Wif key is swept. Simple, and probably will require additions, but would do for now.
Time to fiddle with items.
5.8 Something like this. Subject to change!
Console, early version
5.8 Admin console is a bit of a puzzle. At the moment, I think of showing orders that has been paid AND orders which has note left by admin. Should be sufficient for first release version.
I also deem it bit pointless at the moment to validate values of admin console forms, orders and items.
4.8 pip3 module requirements now include flask-login and flask-session.
It would be interesting to run few instances of Laffka with common order table. This way one can make and keep a lot of small darknetshops in hidden onion land, with overall price well under 50€.
Login and session are required for shopowner identification, means it is in progress, after which packaging only left.
It might be interesting to make liveusb with sole purpose of running small Laffka-torshop.
Word Laffka is from finnish Lavka, which means small shop, usually at market place.
2.8 I should mention, that purchase process is very nonintrusive for customer. Gives a bit strain to shop owner, but not much.
1.8 Meanwhile I suffer from heat and overuse of bandwith, here is small presentation, how payments work.
Suppose customer would like 3pcs of Test item 1:
Generic order of Test item 1
So, customer clicks 3pcs, and arrives at second page:
Address part of ordering
Finally customer arrives at personalized payment page
After which customer is asked to pay for order:
After order being paid, payment reflects on orderpage(http://laffka6wwduoexvb.onion/pay/mryJ3ukrFHoUmdHeSkR4XZcwe3wvG3pRkd)
After payment been through:
Shop owner can claim funds by sweeping own private key from admin console(not finished yet)
Private key cUP4jznEGX8EDMPw813w4B7E6fBo3FDXPqhRLp5sFHq3v3KCgP2z
All right, now lets swipe:
Voila, New transaction received
So, all in all customer paid 4.64526, and shop owner received 4.64108, difference is paid for bitcoin transaction, while private key was swept.
1.8 FFS. Seems I've depleted bandwith for august.
need to tune tor more careful.
UPDATE: temporarily example can be accessed at http://laffka6wwduoexvb.onion/. test22cq47 doesn't work for now.
1.8 Satellite skeleton is done, orders page in progress.
Makes sence to finish satellite with instructions after admin console is done.
Still fucking hot in here, coding advances very slow, yet I believe it is going to be finished before deadline, 12.8
31.7 Satellite is in works, meanwhile testshop can be found at http://test222cq47k6qrn.onion/
http://laffka6wwduoexvb.onion/ is going to point to project site itself, with sources and instructions.
31.7 My bad.Had theoretic items in a shop, and was considered peddling crap by administration.
Exchanged those to Test item 1 and 2, as seen here: http://laffka6wwduoexvb.onion/
Project is now hosted separatedly from development, and should be availible all the time.
Of course, since it is early Alpha, it can fall, but otherwise you are welcome to make test order and pay it with testBitcoins.
It is fucking hot here, literally cannot concentrate myself to do anything useful.There is but two things left before release:
And pip requirements for now: flask, requests, Flask-APScheduler, Flask-WTF, bitmerchant
12.8 is still deadline for release.
Too hot to think about admin console, yet it is not harder to run few instances of Laffka on machine than typing:flask run --port=5678andflask run --port=6789
in two different consoles. Actually nifty. No conflicts, two absolutely separate instances having nothing to do with each other.One can already generate sales, yet database from admin perspective is accessible only from some DB Browser.
29.7 I have observed, that visitors are coming to payment page, where it asks address and then most probably close page.
Don't be afraid, type some stupid shit there, it will transfer you to payment page itself. Don't be afraid to pay order neither, since testBitcoins do not cost anything. Neither I receive any information, except routes of visitors.
Answering questions: Design is no priority whatsoever. Since Laffka is developed with Tor in mind, there is no graphical elements at all. May be later CSS will be tweaked and ability to add pictures to items, but I don't see myself developing cushy designs for Laffka.
It should be lightweight, fast and simple. Functionality is of priority here.
Then there is question "How can I participate". At the moment only by testing is a method or participation, ie making order and paying with testBitcoins. After first release, one can branch code and develop own branch. I am not yet ready to release first public version.
Before releasing, there is necessity to create make/setuptools.py
Always wanted my own small shop on darknet, not consolidated markets, which are riddled with such problems as exit scams, DDOS attacks, rules which you couldn't change and whatnot.
Never found anything suitable, heard about torshop, but apparently it was a scam.
Which is quite understandable - never trust your private keys to unknown third party, it is just plain stupid.
I think I came up with solution. Well, I didn't invent idea of opensource, but I think I know how to make this thing work.
Let me present Laffka, in its very much alpha stage.
It is written in Flask+python3, and uses* sqli*te as database engine. Doesn't require blockchain downloading, checks transactions online and generates private keys for bitcoin wallet sweeping, thus getting payments for *a t*x price.
Should work clearnet too, I don't see why not. Works excellent and made specially for hidden service purpose.
No binaries whatsoever, everything is in clean and understandable python+html. No surprises, no hidden stuff. Plain opensource. And plain opensource will be released, without tricks.
There are some pypi dependencies, I will list them in documentation upon release.
And release is coming soon. Not yet, but I've decided to draw a little attention, since Laffka accepts and processes payments, albeit on very basic level (no admin console at the moment, lot of functionality still missing)
Please observe alpha version 0.02 in action - http://laffka6wwduoexvb.onion/
make order, or observe existing order - http://laffka6wwduoexvb.onion/pay/mxprSXCVX7WvvADDDVCrKmEhfsvWvznawu
(observe increasing wallet balance upon sending testBitcoins. No blockchain involved.)
It would be greatly appreciated if you'd make order and pay for it. TestNet, not MainNet, so no money involved whatsoever. I require some feedback about project. You can run Electrum in testnet electrum --testnet, and get testBitcoins at some faucet, https://testnet.coinfaucet.eu/en/ for example (there are others)
If link doesn't work, it is ok - means I've took it off, and it will be coming back online bit later. Resource will run continuously when I finish satellite for Laffka (ToDo list is on index at http://laffka6wwduoexvb.onion/)
Thanks for attention.
-----BEGIN PGP SIGNED MESSAGE-----
yes, it is me
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
Ulord project progress includes the progress from the underlying layer team, the platform team, the application team, and test team.submitted by ulordchain to u/ulordchain [link] [comments]
Welcome to contact us by email: [email protected], or @UlordChain on Github or twitter. Your advice is very important to us. We look forward to your support and participation. Ulord invites you to build the Ulord ecosystem together!
Development progressThe Ulord public blockchain development mainly focuses on the tutorial of the sidechain UOS testnet, node deployment, TPS testing, and USmart. New features and smart contracts in UDFS has been in development and the UMaster test is complete. Ulord V2.0.0 has been in test and Ulord V2.0.1 has been in development. The developer community V1.2.0 and the block browser of the sidechain UOS testnet have been online.
The public blockchain development
The backstage new function: data statistics, forum management, financial management, proposal management and task management module.
Developer Community V 2.0.0 function test:
b. In the resource bar, users can download USmart tools and the sidechain UOS tutorials.
b. If the proposal is rejected, the users can reapply;
c. The proposal voting failure interface displays related information.
This version was tested and launched on December 28, 2018
TerminologyUOS (Ulord operation system): UOS is the Ulord operation system. It is the second sidechain based on Ulord. It uses the DPos consensus protocol to extend millions TPS. UOS has strong compatibility. The EOS contract applications, with slight configuration, can run on UOS; UOS consensus prevents BP nodes from voting to each other; UOS joins BP penalty mechanism to prevent BP from doing evil; UOS irreversible block mechanism makes block confirmation faster. UOS fundamentally reduces the technical threshold and helps blockchain projects to land quickly.
This post is a collaboration with the Bitcoin community to create a one-stop source for Lightning Network information.
There are still questions in the FAQ that are unanswered, if you know the answer and can provide a source please do so!
?What is the Lightning Network? ?
- Lightning Network
- Lightning Labs
- Lightning FAQ - Audun Gulbrandsen
- Lightning FAQ - Rusty Russell
- Rusty Russell's Coding Blog
- Andreas M. Antonopoulos - Mastering Bitcoin
Specifications / White Papers
- Lightning Network White Paper
- Lightning Network Summary
- Lightning Network Technical Summary
- Lightning Network Specification
- LND API Reference
- Deployable Lightning White Paper
- Scalable Funding of Bitcoin Micropayment Channel Networks
- Bitcoin's Lightning Network, Simply Explained! [5:33]
- The Lightning Network Explained (Litecoin/Bitcoin) [8:13]
- Zap: Lightning Network Wallet (Jack Mallers - Demo Walkthrough) [3:38]
- Cross-Implementation Lightning Payment on Bitcoin's Mainnet (Laolu (a.k.a roasbeef) - Demo) [2:51]
- Bitcoin Q&A: The Lightning Network (Andreas Antonopoulos) [7:55]
- Lightning Network Deep Dive with Laolu "Roasbeef" Osuntokun [48:10]
- SF Bitcoin Devs Seminar: Scaling Bitcoin to Billions of Transactions Per Day [54:40]
- Bitcoin, Lightning, and Streaming Money (Andreas Antonopoulos) [27:38]
- Lightning Network Tech Talk at Coinbase (Thaddeus Dryja and Joseph Poon) [58:11]
Lightning Network Experts on Reddit
- https://www.reddit.com/usestarkbot - (Elizabeth Stark - Lightning Labs)
- https://www.reddit.com/usecdecker - (Christian Decker - Blockstream)
- https://www.reddit.com/useroasbeef - (Olaoluwa Osuntokun - Lightning Labs)
- https://www.reddit.com/usepmpadiou - (Pierre-Marie Padiou - Eclair Developer)
- https://www.reddit.com/useRustyReddit - (Rusty Russell - Blockstream)
- https://www.reddit.com/useDryja - (Tadge Dryja - Digital Currency Initiative)
- https://www.reddit.com/usejosephpoon - (Joseph Poon - Lightning Labs)
- https://www.reddit.com/usefdrn - (Eclair Developer)
- https://www.reddit.com/usestile65 - (Alex Akselrod - Lightning Labs)
- https://www.reddit.com/usecfromknecht - (Conner Fromknecht - Lightning Labs)
Lightning Network Experts on Twitter
- @rusty_twit - (Rusty Russell - Blockstream)
- @starkness - (Elizabeth Stark - Lightning Labs)
- @roasbeef - (Olaoluwa Osuntokun - Lightning Labs)
- @snyke - (Christian Decker - Blockstream)
- @JackMallers - (Jack Mallers - Zap)
- @tdryja - (Tadge Dryja - Digital Currency Initiative)
- @jcp - (Joseph Poon - Lightning Labs)
- @stile65 - (Alex Akselrod - Lightning Labs)
- @bitconner - (Conner Fromknecht - Lightning Labs)
- Lightning FAQ
- Lightning Network Bitcoin Wiki
- Hashed Timelock Contracts
- LN as a Directed Graph; Single-Funded Channel Topology (Slides)
- How to Do "2-of-3 Multisig Contract" Equivalent on Lightning (From LN Mailing List)
- lightning-app - Cross-platform Lightning Desktop Application
- lnd-gui - Lightning MacOS GUI Wallet
- eclair-node-gui - Cross-platform desktop GUI for Lightning
- zap-desktop - Lightning Network desktop application
- lncli-web - Light-weight web client for the lnd daemon written in NodeJS / Angular
- kugelblitz - A simple UI for the c-lightning daemon lightningd and bitcoind
Tutorials and resources
- Install bitcoind + lnd
- Develop an application of bitcoind and lnd
- Setting up and Testing LND with the Testnet Lightning Faucet
- Setting up a local Lightning cluster
- Using the LND Web Client
- Using the LND gRPC Client
- Integrating Lightning into a server-side web application
- How to use a Python gRPC Client with LND
Lightning on Testnet
- HTLC Web Lightning Wallet
- Eclair wallet (for android)
- Eclair wallet (Linux, macOS, Windows)
- Zap wallet (Linux, macOS, Windows)
Place a transaction
Instant Swaps for Altcoins using Lightning
Lightning on Mainnet
- Instant Cross-Chain Transactions On Lightning
Developer Documentation and Resources
- LND - Lightning Network Daemon (Golang)
- eclair - A Scala implementation of the Lightning Network (Scala)
- lit - Lightning Network node software (Golang)
- c-lightning - A Lightning Network implementation in C
- lightning-onion - Onion Routed Micropayments for the Lightning Network (Golang)
- lightning-integration - Lightning Integration Testing Framework
- ptarmigan - C++ BOLT-Compliant Lightning Network Implementation [Incomplete]
[Of course, that scene finishes with knocking out the "recovering" patient so he can be taken away...not to mention the absurdity of including Monty Python in a financial article, but moving right along.]