Neutrino - Revision history

MiltonPusser at 14:09, 28 March 2019

2019-03-28T14:09:01Z

← Older revision		Revision as of 14:09, 28 March 2019
Line 1:		Line 1:
	{{ALERT\|There are multiple known major issues with the client, so it is not recommended to use it with real money at this point.}}		{{ALERT\|There are multiple known major issues with the client, so it is not recommended to use it with real money at this point.}}
	Neutrino is an experimental Bitcoin light client written in Go and designed with mobile Lightning Network clients in mind. It uses a new proposal for compact block filters to minimize bandwidth and storage use on the client side, while attempting to preserve privacy and minimize processor load on full nodes serving light clients.		Neutrino is an experimental [[Bitcoin]] light client written in Go and designed with mobile Lightning Network clients in mind. It uses a new proposal for compact block filters to minimize bandwidth and storage use on the client side, while attempting to preserve privacy and minimize processor load on full nodes serving light clients.

	The light client '''synchronizes only block headers''' and a chain of '''compact block filter''' headers specifying the correct filters for each block. Filters are loaded lazily and stored in the database upon request; blocks are loaded lazily and not saved.		The light client '''synchronizes only block headers''' and a chain of '''compact block filter''' headers specifying the correct filters for each block. Filters are loaded lazily and stored in the database upon request; blocks are loaded lazily and not saved.

MiltonPusser at 14:08, 28 March 2019

2019-03-28T14:08:38Z

← Older revision		Revision as of 14:08, 28 March 2019
Line 1:		Line 1:
	Neutrino ~~introduces more~~ privacy for ~~lightweight nodes~~.		{{ALERT\|There are multiple known major issues with the client, so it is not recommended to use it with real money at this point.}}
			Neutrino is an experimental Bitcoin light client written in Go and designed with mobile Lightning Network clients in mind. It uses a new proposal for compact block filters to minimize bandwidth and storage use on the client side, while attempting to preserve privacy and minimize processor load on full nodes serving light clients.

			The light client '''synchronizes only block headers''' and a chain of '''compact block filter''' headers specifying the correct filters for each block. Filters are loaded lazily and stored in the database upon request; blocks are loaded lazily and not saved.

	Unlike full nodes which have a full historical record of transactions, lightweight nodes only sync block headers and use a method called [https://bitcoin.org/en/glossary/simplified-payment-verification Simple Payment Verification]		Unlike full nodes which have a full historical record of transactions, lightweight nodes only sync block headers and use a method called [https://bitcoin.org/en/glossary/simplified-payment-verification Simple Payment Verification]

	https://github.com/lightninglabs/neutrino		https://github.com/lightninglabs/neutrino

MiltonPusser at 10:06, 20 January 2019

2019-01-20T10:06:42Z

← Older revision		Revision as of 10:06, 20 January 2019
Line 1:		Line 1:
			Neutrino introduces more privacy for lightweight nodes.

	Unlike full nodes which have a full historical record of transactions, lightweight nodes only sync block headers and use a method called [https://bitcoin.org/en/glossary/simplified-payment-verification Simple Payment Verification]		Unlike full nodes which have a full historical record of transactions, lightweight nodes only sync block headers and use a method called [https://bitcoin.org/en/glossary/simplified-payment-verification Simple Payment Verification]

			https://github.com/lightninglabs/neutrino

MiltonPusser: Created page with "Unlike full nodes which have a full historical record of transactions, lightweight nodes only sync block headers and use a method called [https://bitcoin.org/en/glossary/simpl..."

2019-01-20T10:06:06Z

Created page with "Unlike full nodes which have a full historical record of transactions, lightweight nodes only sync block headers and use a method called [https://bitcoin.org/en/glossary/simpl..."

New page

Unlike full nodes which have a full historical record of transactions, lightweight nodes only sync block headers and use a method called [https://bitcoin.org/en/glossary/simplified-payment-verification Simple Payment Verification]