Open Research Problems

This document summarizes several open research problems related to Grin. Feel free to join us on Keybase to discuss them. Funding available.

Table of Contents

Number Name
1 BLS Signatures
2 Accumulator
3 Research on ZKPs Recent Advances
4 Scriptless Scripts
5 FlyClient
6 Asynchronous Transaction Building
7 Reducing Linkability of Outputs On Chain
8 Erlay Transaction Relaying
9 Payment Channel Hubs

1. BLS Signatures


Introduced in 2001 by Boneh, Lynn and Shacham, BLS signatures introduces non-interactive kernel aggregation and potentially simpler multisignature schemes.

While it is not for certain that such signatures are well suited for Grin it is still interesting to explore this design.

Relevant Papers

Other resources

Github Issue

2. Accumulator


In Grin, kernels, outputs and range proofs are stored in a type of accumulator called a Merkle Mountain Range. While efficient, there have been several improvements to this kind of data structure, for example RSA Accumulators. The goal of this research problem is to identify whether or not Grin can leverage more advanced or faster cryptographic accumulators.

Relevant Papers

3. Research on ZKPs Recent Advances

This research subject is about investigating recent advances in zero knowledge proofs and how Grin can leverage their potential improvements. Improvements can be on:

Relevant papers

4. Scriptless Scripts


Mimblewimble does not support any kind of script. In 2017, Andrew Poelstra introduced a way to add smart contract ability to this type of blockchain: scriptless scripts.

While a significant research effort has been done on the subject there are very few concrete implementations of such cryptographic structure.

The goal of this research problems is to investigate scriptless scripts in Grin and potentially implement basic contract features.

Relevant Presentations

5. FlyClient


"To validate transactions, cryptocurrencies such as Bitcoin and Ethereum require nodes to verify that a blockchain is valid. This entails downloading and verifying all blocks, taking hours and requiring gigabytes of bandwidth and storage. Hence, clients with limited resources cannot verify transactions independently without trusting full nodes.[…] FlyClient is a novel transaction verification light client for chains of variable difficulty. FlyClient is efficient both asymptotically and practically and requires downloading only a logarithmic number of block headers while storing only a single block header between executions."

The goal of this research problems is to investigate/implement the necessaries prerequisites for the introduction of FlyClient in Grin.

Relevant Papers

Github Issue

6. Asynchronous transaction building


One of the trade-offs of the Mimblewimble type blockchain is that it requires a round trip between the payer and payee to construct a valid transaction. Meaning that the sender and receiver must be online to transact.

Several research attempts have been made in that direction. For example, relying on federated relays or Beam shared bulletin board system.

The goal is this research problem is to investigate and develop an asynchronous, robust, and privacy preserving method of building Grin transactions.

Github Resources

7. Reducing Linkability of Outputs On Chain


Mimblewimble/Grin leverage confidential transactions to hide the identity of the sender and recipients. As such, there are no public amounts or addresses.

However, it is possible for someone listening on the network to build a transaction graph and possibly clustering entities together.

Techniques like Dandelion++ mitigate this issue but are insufficient for a privacy coin.

A much more promising design is this Mimblewimble CoinSwap proposal

The goal of this research is to investigate ways to obfuscate the Grin transaction and implement such design.

Relevant Papers

8. Erlay Transaction Relaying

Erlay is a transaction dissemination protocol proposed by G. Naumenko, G. Maxwell, P. Wuille. The motivation is to improve connectivity between Bitcoin nodes and reduce the bandwidth required to operate a full node. It claims to reduce the bandwidth consumption by 40% assuming current connectivity, and keeps bandwidth use almost constant as connectivity increases. It also hardens the network against attacks that attempt to learn the origin node of a transaction.

This protocol could prove useful to Grin as well, and it is of value to the community to investigate how this best should be implemented.

Relevant Papers

Github issue

Forum thread

9. Payment Channel Hubs

Payment channel hubs offer the possibility of instant payments that improve privacy by joining transactions (like a coinjoin server), and improving scalability by pruning intermediate txs and potentially even aggregating kernels. Grin already has NRD (NoRecentDuplicate) kernels waiting to be activated, which provide the relative timelocks needed for implementing basic payment channels. The difficulty is in trying to design a PCH that is trustless (can’t steal/freeze coins or rollback txs), and that doesn’t learn everything about the individual transactions (amounts, input/output links, etc). These past few years have seen a lot of developments in this area (TumbleBit, Bolt, A2L, etc.) but nothing that can be directly applied to Grin in a way that doesn’t requiring trusting hub operators to preserve your privacy.

Relevant papers