Bitcoin Forum
April 06, 2026, 08:22:09 PM *
News: Latest Bitcoin Core release: 30.2 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Novel Bitcoin Payment Service  (Read 449 times)
EllenRApps (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile WWW
September 27, 2024, 10:34:48 AM
Last edit: March 20, 2026, 02:25:45 AM by EllenRApps
 #1

Project Name:
Novel Bitcoin Payment Service

Project GitHub:
https://github.com/ellenrapps/Novel-Bitcoin-Payment-Service-
Yamane_Keto
Hero Member
*****
Offline Offline

Activity: 826
Merit: 569


♻️ Automatic Exchange


View Profile WWW
September 29, 2024, 03:02:04 PM
Merited by Pmalek (2)
 #2

The GitHub file doesn't have an introduction to how to install the file or some necessary questions so I dug a little bit into the code:

Code:
        self.sender_key_label = tk.Label(self.frame, text="Enter Sender Private Key (Limit to 64 Alphanumeric)", font=("Arial", 9), bg='#8fbc8f')
        self.sender_key_label.pack()
        self.input_sender_key = tk.Entry(self.frame, validate="key", textvariable=self.sender_key_var, width=85, font=("Arial", 9), borderwidth=2, relief="raised", show="*")
        self.input_sender_key['validatecommand'] = (self.input_sender_key.register(self.val_k),'%P','%d')
        self.input_sender_key.pack()


Why does the Bitcoin payment services processor need to get the private key? This can be done by usiing the MPK and creating the wallet without risking exposing the private key.

░░░░▄▄████████████▄
▄████████████████▀
▄████████████████▀▄█▄
▄██████▀▀░░▄███▀▄████▄
▄██████▀░░░▄███▀▀██████▄
██████▀░░▄████▄░░░▀██████
██████░░▀▀▀▀▄▄▄▄░░██████
██████▄░░░▀████▀░░▄██████
▀██████▄▄███▀░░░▄██████▀
▀████▀▄████░░▄▄███████▀
▀█▀▄████████████████▀
▄████████████████▀
▀████████████▀▀░░░░
 
 CCECASH 
EllenRApps (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile WWW
September 30, 2024, 05:47:16 AM
Last edit: January 01, 2025, 12:27:34 AM by EllenRApps
 #3

The GitHub file doesn't have an introduction to how to install the file or some necessary questions so I dug a little bit into the code:

Code:
        self.sender_key_label = tk.Label(self.frame, text="Enter Sender Private Key (Limit to 64 Alphanumeric)", font=("Arial", 9), bg='#8fbc8f')
        self.sender_key_label.pack()
        self.input_sender_key = tk.Entry(self.frame, validate="key", textvariable=self.sender_key_var, width=85, font=("Arial", 9), borderwidth=2, relief="raised", show="*")
        self.input_sender_key['validatecommand'] = (self.input_sender_key.register(self.val_k),'%P','%d')
        self.input_sender_key.pack()


Why does the Bitcoin payment services processor need to get the private key? This can be done by usiing the MPK and creating the wallet without risking exposing the private key.

Thank you for your reply and interest.

The reason why the GitHub file doesn't have an introduction on how to install the file is because I haven't yet released a "Package" as this project is still in its early stage. Once the first Package version will be released, a number of security measures will be introduced.

You did the right thing of digging into the code itself.

The upcoming Package release and the updates thereafter will self-destruct all users data. This service will have no memory of users' data.
  
Line 3 of the quoted code has this: show="*", which means that data is not revealed just like entering a password. As the service doesn't keep any user's data, the only way to send funds is to enter that data as the address alone isn't enough to release funds. Rest assured that this part will be secured further.

The aim is for users not to be dependent on this payment service alone.
Yamane_Keto
Hero Member
*****
Offline Offline

Activity: 826
Merit: 569


♻️ Automatic Exchange


View Profile WWW
October 01, 2024, 12:07:06 PM
 #4

You did the right thing of digging into the code itself.

The upcoming Package release and the updates thereafter will self-destruct all users data. This service will have no memory of users' data.
  
Line 3 of the quoted code has this: show="*", which means that data is not revealed just like entering a password. As the service doesn't keep any user's data, the only way to send funds is to enter that data as the address alone isn't enough to release funds. Rest assured that this part will be secured further.


There is still a slight possibility that a third party may be able to record the data before it is destroyed so it is better to use MKP rather than asking the user for the private key.

░░░░▄▄████████████▄
▄████████████████▀
▄████████████████▀▄█▄
▄██████▀▀░░▄███▀▄████▄
▄██████▀░░░▄███▀▀██████▄
██████▀░░▄████▄░░░▀██████
██████░░▀▀▀▀▄▄▄▄░░██████
██████▄░░░▀████▀░░▄██████
▀██████▄▄███▀░░░▄██████▀
▀████▀▄████░░▄▄███████▀
▀█▀▄████████████████▀
▄████████████████▀
▀████████████▀▀░░░░
 
 CCECASH 
EllenRApps (OP)
Newbie
*
Offline Offline

Activity: 3
Merit: 0


View Profile WWW
October 01, 2024, 10:46:59 PM
Last edit: July 26, 2025, 10:45:54 PM by EllenRApps
 #5

There is still a slight possibility that a third party may be able to record the data before it is destroyed so it is better to use MKP rather than asking the user for the private key.

Indeed, MKP has advantages. However, it has disadvantages as well.
Pages: [1]
  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!