New Epic Wallet Transaction Method As part of our ongoing efforts to make Epic more flexible, poolboy has added a new transaction method that uses email to share the transaction file between sender and receiver. We should see this in an upcoming release of both CLI wallet and GUI (stay tuned for further announcements on this). This new method uses IMAP and SMTP servers, so if you and the receiver have an established IMAP email account that uses ports 993 and 465 (TLS) for login and transport, you can send a transaction using an email address instead of http, tor, emoji, files, or epicbox. The sender creates a new transaction and sends it to the receiver via smtp using the receiver's email address: ./epic-wallet send -m "mail" 20 -d receiver@domain.com (CLI: The new argument for send method is "mail"). This creates a transaction file and attaches it to an email message that is sent to the receiver's email address. The receiver has to start a listener to process the transaction: ./epic-wallet listen -m imap The receiver will need to move the email message from their Inbox to the Inbox/EpicCash folder for the listener to find it. The receiver can automate the incoming message with an email client rule that looks in the subject for "EPIC Transaction" then moves that message to the Inbox/EpicCash folder and sets it to 'Unread'. The listener will check in with your email server every minute for unread messages in the mailbox "Inbox/EpicCash". Once the listener finds an unread message in that mailbox, it imports the transaction file from the attachment, processes the transaction and receive confirmation, and sends back the signed transaction file to the sender as an attachment in a reply email. The sender has to start a listener to check in with their email server for a reply from the receiver (same way receiver does looking in Inbox/EpicCash) to process the transaction file and finalize. Sender can set a rule looking for "EPIC Confirmation" in the subject to automate moving to Inbox/EpicCash folder. To automate both sending and receiving, set a rule to look for either "EPIC Transaction" or "EPIC Confirmation" and move to the Inbox/EpicCash folder. So basically, this is using the transaction file process and automating the file sharing by attaching it to email messages. It still requires the 3-way send-confirm-finalize steps but offers an alternative to using epicbox as the middle man, depending on whether you trust epicbox more or less than your email service provider's server and provides a simpler address scheme (familiar email addresses vs epicbox addresses). Manual First Step: You can create a transaction file and attach it to an email to the receiver. It will end up in their Inbox. When they run their wallet listener for imap, it will create the EpicCash subfolder in their Inbox (if it doesn't already exist) and they will have to move the message from Inbox to Inbox/EpicCash and mark it as unread. Then their listener will continue with the automated process. New config sections for epic-wallet.toml ############################### ### IMAP CONFIGURATION ### ############################### [imap] server = "IMAP SERVER" username = "IMAP USERNAME" password = "IMAP PASSWORD" port = 993 inbox = "INBOX.EpicCash" reply_subject = "EPIC Confirmation" reply_body = "Move this mail into the EpicCash mailbox and mark as unread,<br/>to finalize the transaction. <h1>HTML-Mail Template</h1>" ############################### ### SMTP CONFIGURATION ### ############################### [smtp] server = "SMTP SERVER" username = "SMTP USERNAME" password = "SMTP PASSWORD" from_address = "YOUR MAIL" subject = "EPIC Transaction" body = "Move this mail into the EpicCash mailbox and mark as unread,<br/>to process this transaction. <h1>HTML-Mail Template</h1>"