Bitcoin Forum
November 19, 2026, 09:11:54 PM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 [14]  All
  Print  
Author Topic: Sparrow Bitcoin Wallet  (Read 5627 times)
nc50lc
Legendary
*
Offline

Activity: 3332
Merit: 9372


Self-proclaimed Genius


View Profile
November 17, 2026, 06:01:45 AM
 #261

Where (based from nullius' post), their CSV file is designed to be compatible with Electrum's pay-to-many since they just copy-paste it.
An edit to include a label on the first output's third column and remove all the commas should do the trick.
The spreadsheet can be updated to provide the proper formatting for both Electrum and Sparrow.  The formula I show in column C can be moved to another sheet, and still provide copy and past convenience for Electrum.  The data on the primary sheet can have a third column for the label, and be saved as a CSV to be imported into Sparrow.
That's a good suggestion to support both clients.

The original spreadsheet is probably similar to your example's column C
Or consisting of three columns with address, comma then amount, respectively.
Both can be directly copied as text that Electrum supports.

satscraper
Legendary
*
Offline

Activity: 1652
Merit: 3180


AntiSwap.io - NO AML/KYC EXCHANGER MONITORING


View Profile
November 17, 2026, 08:24:43 AM
 #262

and remove all the commas should do the trick.

Value data in csv files that Sparrow can consume must be separated by commas. Comma delimiter does the trick. I’ve tried other common delimiters, such as semicolons, pipes, and spaces, but none of them work, i.e. Sparrow can’t open the relevant files. So, if users want to use Send to many, they should use commas.

Regarding labels, I think this is a very useful feature for businesses sending in bulk, since addresses without labels are almost uninformative.



 AntiSwap 
█████▄▄▄█████▄▄▄
█▄████████████████▄▄▄
▐█████████████████████▄
█████████▀▀█▀██████████
███████▀▄▄▄██▀████████▌
██████████▄▄█████████▀
██████▀▀████▀███████▀
▐█████▄████▄███████▀
████████▄█████████▀
█████████████████
███████████████▀
████▀████████▀
██████▀███▀

│❌ NO AML / KYC
███████████████████████
█████▀█▀▀▀▀██████████████
█████▀▀▀▀▀▀███████████████
███████████████████████████
███████████████████████████
██████████████████████████
████████████████████████▀█▄
███████████████████████▀██▄█▄
█████████████████████████▀████▄
███████████████████████████▀████▄
█████████████████████████████▀██▀
🔎︎ 900+
EXCHANGERS

██ ██ ██ ██ ██ ██
│
3 TIER
RATING
SYSTEM

🟢 Fair
🟠 Neutral
🔴 SCAM!
│
 BTC   ➤ 
nc50lc
Legendary
*
Offline

Activity: 3332
Merit: 9372


Self-proclaimed Genius


View Profile
Today at 03:55:04 AM
 #263

and remove all the commas should do the trick.
Value data in csv files that Sparrow can consume must be separated by commas. Comma delimiter does the trick. I’ve tried other common delimiters, such as semicolons, pipes, and spaces, but none of them work, i.e. Sparrow can’t open the relevant files. So, if users want to use Send to many, they should use commas.
CSV file content such as this is accepted by Sparrow:


No commas or other delimiters, just consisting of 3 columns as their tooltip suggests.
You're talking about Electrum's pay-to-many perhaps? Its address and amount are separated by comma.

satscraper
Legendary
*
Offline

Activity: 1652
Merit: 3180


AntiSwap.io - NO AML/KYC EXCHANGER MONITORING


View Profile
Today at 07:56:58 AM
 #264

and remove all the commas should do the trick.
Value data in csv files that Sparrow can consume must be separated by commas. Comma delimiter does the trick. I’ve tried other common delimiters, such as semicolons, pipes, and spaces, but none of them work, i.e. Sparrow can’t open the relevant files. So, if users want to use Send to many, they should use commas.
CSV file content such as this is accepted by Sparrow:


No commas or other delimiters, just consisting of 3 columns as their tooltip suggests.
You're talking about Electrum's pay-to-many perhaps? Its address and amount are separated by comma.

Nope, I was talking about Sparrow.

I see that the data in your CSV are already separated into columns, so I guess it probably has the hidden delimiter. What software did you use?

I created CSV manually and used commas as delimiters. Sparrow was able to read that file, but it couldn’t read files with other delimiters.


 AntiSwap 
█████▄▄▄█████▄▄▄
█▄████████████████▄▄▄
▐█████████████████████▄
█████████▀▀█▀██████████
███████▀▄▄▄██▀████████▌
██████████▄▄█████████▀
██████▀▀████▀███████▀
▐█████▄████▄███████▀
████████▄█████████▀
█████████████████
███████████████▀
████▀████████▀
██████▀███▀

│❌ NO AML / KYC
███████████████████████
█████▀█▀▀▀▀██████████████
█████▀▀▀▀▀▀███████████████
███████████████████████████
███████████████████████████
██████████████████████████
████████████████████████▀█▄
███████████████████████▀██▄█▄
█████████████████████████▀████▄
███████████████████████████▀████▄
█████████████████████████████▀██▀
🔎︎ 900+
EXCHANGERS

██ ██ ██ ██ ██ ██
│
3 TIER
RATING
SYSTEM

🟢 Fair
🟠 Neutral
🔴 SCAM!
│
 BTC   ➤ 
nc50lc
Legendary
*
Offline

Activity: 3332
Merit: 9372


Self-proclaimed Genius


View Profile
Today at 11:04:48 AM
 #265

I created CSV manually and used commas as delimiters. Sparrow was able to read that file, but it couldn’t read files with other delimiters.
Okay we're talking about the same thing but viewing it differently.
You've manually created it so you probably used a text editor to view and create the file, while I've created it on a spreadsheet.

DireWolfM14
Legendary
*
Offline

Activity: 3052
Merit: 6145


فلسطين


View Profile WWW
Today at 05:38:58 PM
 #266

What software did you use?

Any spreadsheet software will save a sheet in CSV format.  Obviously Excel and it's open-source doppelganger, GridCraft are capable, and so is the most common open-source spreadsheet software, LibreOffice Calc (which appears to be what nc50lc is using.)

I created CSV manually and used commas as delimiters. Sparrow was able to read that file, but it couldn’t read files with other delimiters.

Keeping track of data in a spreadsheet is much more convenient, practical, and useful than entering it manually into a text editor, and exporting a CSV from a spreadsheet is a piece of cake.

nullius
Copper Member
Hero Member
*****
Offline

Activity: 672
Merit: 2881


Privacy is necessary & sufficient for fungibility.


View Profile WWW
Today at 08:29:03 PM
 #267

Thanks for the informative discussion about CSV.  My apologies for falling behind on my own question.

It’s not my spreadsheet, and I don’t know how it works—however, yes, I think that every spreadsheet in the world can export to CSV.  It’s the lingua franca of tabular data.  SQLite’s shell tool can also import CSV, which I myself find more useful.

I don’t know about this particular person’s workflow—but merely in my own opinion, I think that CSV would be a much better interface than copy-pasting for SME business use with numerous bulk payments.



Unfortunately, my reason for looking at Sparrow in the first place has been obviated.  I’m looking for a user-friendly Silent Payments sending and receiving wallet, to recommend to people who are not me.

I’ve been learning more about SP and SP lightwallet protocols.  Thereupon, I cannot in conscience recommend anything that uses the Sparrow/Frigate strategy.

Sparrow reveals the SP scan key to the server.  (Not the spend key:  The scan key.)  Frigate only processes these keys in memory, and does not store them—but there’s nothing to stop Chainalysis from making a small patch to Frigate, and setting up a hundred GPU cloud honeypot servers that log absolutely everything.

The only defense against this is to train users against using this type of protocol.  Tweak servers like Blindbit don’t get any information that could be used to spy on your SP coins.

Revealing the scan key is much worse than revealing ordinary Bitcoin addresses within a wallet’s gap limit, which is bad enough.  The scan key can be used to see all past, present, and future payments to an SP address, for all possible labels—forever.  It’s a static, long-term encryption key; entrusting it to a server sounds to me like entrusting your PGP private key to a webmail server.  If your webmail server unverifiably promises to process your PGP private key only in memory (pinky-swear!), is that secure email?

If you want to stop the accruing privacy damage of connecting to an untrusted Electrum server, there is no way to undo the past—but for P2WPKH (etc.) addresses, you can protect your future privacy simply by bumping your wallet past its current gap limit (don’t forget change addresses!).  Then, remember to skip the gap limit again if you ever need to restore from seed...  Anyway, you don’t need to make a new wallet.  Whereas with SP, if you have revealed the scan key, the only way to prevent future spying is to make a totally new SP address.  This adds to the cost of SP scanning, as you’ll still want to scan the old address in case someone sends funds to it.

Nontechnical users (and even most technical users) have a poor understanding of privacy threats.  I think that the Electrum protocol ecosystem runs entirely on hopium, blind faith in untrusted parties, and wishful thinking.  Ignorance is bliss; if you never know which public server logged what, why should you care, right?  This is worse with SP, as it will result in a false sense of security with the equivalent of infinite address reuse.  People will behave differently, if they believe that blockchain analysts can’t trivially link all of their coins under common ownership.  Worse:  Their counterparties will behave differently, with neither choice nor informed consent in the matter.

And it’s all so unnecessary.  There are lightwallet SP scan strategies that reveal nothing to the server, at only moderate load to the client.  It’s not a situation where dangerous levels of trust are the least-worst of bad options for many practical use cases.  SP can and should be always fully trustless.

Please don’t say, “Well, people can run their own personal Electrum/Frigate servers.”  That’s not the reality of >99% of the lightwallet user base; security and privacy must be designed accordingly, lest one create an ideal operating environment for honeypots.  Oh, and as for the people who say, “Trust my Frigate server not to log your scan key; I’m an honest community member who definitely doesn’t want to remember your key,” sorry but not:  That makes me trust you less.

▄▄████████████████████▄▄
▄███████▀▀██████▀▀███████▄
█████▀██████████████▀█████
████████▄▄██████▄▄████▀███
██████████████████████████
██▄▄██████████████▄▄██████
██▀▀██████████████████▄▄██
██████▀▀██████████████▀▀██
██████████████████████████
███▄████▀▀██████▀▀████████
█████▄██████████████▄█████
▀███████▄▄██████▄▄███████▀
▀▀████████████████████▀▀

 DΞX.fo 
▄▄██████
█████████
██████████
██████████
██████████
█████████
▀▀██████

▄███████
▄██████████
████████████
█████████████
█████████████
|███████▄███▄███▄███▄██
█████████▄▀█████▀▄████
███▄████████▀█▀████████▄
█████████▀███████▀██████
████████████████████████
█▄██▄▀▀▀▀▀██▄▀▄██▀▀▀▀▀▄▀
▄████▄▀▀▀██▀███▀██▀▀▀▄
████████████████████
▀███████████████████▄
█▀████████████████████▄▄
████████████████████████
████████████████████████
███▀███████████████████▀
|
Pages: « 1 2 3 4 5 6 7 8 9 10 11 12 13 [14]  All
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!