April 17, 2026

Capitalizations Index – B ∞/21M

Lightning + NFC? The New Plan to Bring Bitcoin to Retail

Lightning + nfc? The new plan to bring bitcoin to retail

Lightning + NFC? The New Plan to Bring Bitcoin to Retail

Lightning + nfc? The new plan to bring bitcoin to retail

Imagine a way to expand bitcoin payments to millions per second. Now, imagine a clunky, command-line interface.

That’s the extent of the divide between the vision enabled by bitcoin’s best-yet scaling solution, the lightning network, and the current state of its design. But while that’s daunting, developers are moving ahead on designs to make the payment system easier to use, with one recently submitting a proposal for connecting lightning with a payment technology that could make it feel as futuristic as it’s touted.

That payment technology, near-field communication, or NFC, would allow a user to pay for an item just by holding their smartphone an inch away from the device it’s paying.

Not a new idea in bitcoin or the payments world at large, NFC-based payments have caught on throughout Asia and Europe – not only on smartphones, but also through chips embedded in payment cards. And while the U.S. might be lagging behind in NFC adoption, bitcoin’s early adopters might just be the right target audience.

As such, the proposal, submitted by developer Igor Cota, looks to standardize a way to connect lightning with NFC.

Invoking the name of his lightning wallet that uses NFC, Presto, Cota told CoinDesk:

“I want the payments to be instant just like with the contactless cards we have here in Europe. A user would simply tap on the payment terminal and presto!”

Further, Cota imagines turning any computer into a lightning point-of-sale terminal through the use of a $29 USB attachment, a route that has proven successful in his early tests.

Replacing QR codes

Given the success, Cota’s proposal is about standardizing what he’s created, adding it to the many other standard rules that describe how each lightning software implementation should operate.

Many bitcoin payments implementations tend to use QR codes – those pixelated-looking black-and-white squares that encode data that can then be scanned and consumed by smartphones. And while Presto supports QR codes alongside NFC, he believes the latter provides a much better experience.

QR codes not only can be a bit finicky, but they also can become “unwieldy,” Cota said, especially when more information is added to them. In this way, merchants won’t be able to add much information such as itemized receipts and coupons to QR codes, he said.

NFC, though, doesn’t have this hurdle.

“I’d like to see a system where the payment terminal sends a nice HTML receipt for the customer – that receipt has, say, a table list of your grocery shopping with subtotal, taxes, grand-total, perhaps a shop logo, some loyalty code or a coupon for future use,” he said.

In Cota’s mind, this would give consumers a more detailed record of their spending habits, empowering them to take even more control of their finances.

“Imagine a wallet that can tell you how much you’ve spent on broccoli last month?” Cota said, adding:

“With crypto you’re always in control, but with these digital receipts you are even more so.”

A bolt of lightning

But first, Cota is trying to get his NFC implementation added to the standards that lightning network developers have established in an effort to make sure all implementations are compatible with each other.

These standards are called “BOLTS,” and Cota believes NFC should be added to BOLT 11, which explains how “invoices” – describing how much a person owes – should be encoded and presented to a user. It’s a similar process to that of the credit card reader at Starbucks showing you that you owe $4.50 for a mocha latte.

For now, BOLT 11 only describes a standard for QR codes.

Already, Cota has come up with a rough standard, putting together a Multipurpose Internet Mail Extensions (MIME) type, which is a format for sending data; an NFC application ID, which indicates the payment method is lightning; and a “very simple protocol to forward socket data.”

Though these pieces weren’t so hard to come up with, Cota said he thinks it’s important to write up a standard, whereby all NFC-enabled point-of-sale devices can accept any NFC-based lightning payment, now to be ahead of the game should NFC-based lightning payments take off.

“For the sake of interoperability, it would be great if we agreed on some standards,” he explained.

And already, most of the public technical feedback has been positive, with Lightning developers ZmnSCPxj and Corné Plooy responding favorably to the proposal on the mailing list.

However, Bitrefill lightning developer Justin Camarena was a bit wishy-washy, telling CoinDesk:

“It’s an obvious way to pay in the future but it seems we’re a bit too early as there are no hardware point-of-sales offering lightning support.”

Still, Cota is plugging away on the next steps to move the project forward.

“As you can see the [Presto user-interface] is not really there yet but I’m working on it,” he said, adding, “What I’m working on at the moment is a protocol that makes sure the NFC payment goes through even in case the paying device is offline.”

Cota plans to submit another pull request for developers to review once this mechanism is finished.

NFC image via Igor Cota

The leader in blockchain news, CoinDesk is a media outlet that strives for the highest journalistic standards and abides by a strict set of editorial policies. CoinDesk is an independent operating subsidiary of Digital Currency Group, which invests in cryptocurrencies and blockchain startups.

Published at Tue, 17 Apr 2018 04:00:35 +0000

Features

Previous Article

Mehr Sicherheit durch Blockchain: MasterCard meldet Patent an

Next Article

Ethereum Price Technical Analysis – Can ETH/USD Hold This?

You might be interested in …

Bitcoin Miners Miss the First BIP 148 “Deadline”

Bitcoin Miners Miss the First BIP 148 “Deadline”

bitcoin miners at large have missed the first BIP 148 “deadline” to prevent a “split” in bitcoin’s blockchain.

As bitcoin’s scaling dispute appears to be heading for a climax, the next couple of weeks could prove pivotal. One scaling solution in particular, Bitcoin Improvement Proposal 148 (“BIP 148”), is scheduled to trigger activation of Segregated Witness (SegWit) on August 1, 00:00 UTC. As a User Activated Soft Fork (UASF), all users that run a BIP 148 node will then start rejecting any and all blocks that do not signal support for SegWit by the “deadline” — or, perhaps more accurately, “ultimatum” — set by BIP 148 users.

BIP 148 and SegWit are backward-compatible protocol upgrades, which means that non-upgraded nodes will still accept SegWit-signaling and SegWit-utilizing blocks. Therefore, if a majority of hash power in one way or another adopts SegWit before August 1, all current bitcoin nodes would follow the same blockchain.

However, if only a minority of miners activates SegWit through BIP 148, bitcoin’s blockchain and currency would “split” in two. This would result in two types of “bitcoin”: one that activated BIP 148 and one that did not, while even more types of “bitcoin” could emerge as a result. A split between BIP148-nodes and non-BIP148 nodes would last at least until a majority of hash power joins the BIP 148 chain, or until the BIP 148 chain is abandoned by all users and miners for good.

Miners essentially have three options to avoid such a split. This first option was to lock in SegWit before August 1 through the activation mechanism proposed by Bitcoin Core and implemented in many nodes on the network. This required 95 percent of hash power to signal support for the upgrade within a two-week difficulty period. Specifically, such a difficulty period consists of 2,016 of these sequential blocks, which means that a minimum of 1,916 blocks must signal support. Or, in other words, if more than 100 blocks — at least 101 of them — do not signal support for SegWit within a single difficulty period that ends before August 1, this BIP 148 deadline is missed.

Ignoring extreme statistical deviations or other unexpected events, the final difficulty period to end before August 1 started on Friday (UTC). And out of the first day and a half worth of blocks within this difficulty period, only about half of them signaled support for Segregated Witness. This means that the threshold of 101 blocks not signaling support has now been reached.

With two more BIP 148 deadlines ahead, the first one was probably also the most likely to be missed. Its threshold was the hardest of the three to achieve as it required the highest level of hash rate to succeed. Additionally, a large majority of miners (by hash power) indicates that they will activate SegWit through BIP 91 instead. This is the next BIP 148 deadline.

This next deadline will be on July 29. This is the last day that BIP 91 can activate in time to be compatible with BIP 148. In order to do so, 80 percent of hash power must have signaled support for SegWit2x within 2 1/3 days. As such, miners should at the very latest start signaling support for BIP 91 on the 26th of July. Though like the now-missed BIP141 deadline, which is technically not until August 31, the BIP 91 deadline could actually be either missed or met before July 29 as well.

If this next BIP 91 deadline is missed too, miners will have one more chance to avoid a “split.” A majority of hash power would have to activate SegWit through BIP 148 itself by August 1, 00:00 UTC. Alternatively, a majority of hash power could switch to the BIP 148 chain even after August 1 to reunite both chains, but this will likely cause significant disruption on the bitcoin network(s), and potentially a loss of funds for users not aware of the risks.

For more information on how to keep your bitcoins safe during a potential coin-split, click here.

The post Bitcoin Miners Miss the First BIP 148 “Deadline” appeared first on Bitcoin Magazine.