Topic: ELECTRUM - BITCOIN WALLET - page 30. (Read 39980 times)

3. Wallet.dat kita bisa kita export dari Android dan import di Electrum Desktop Windows?

tidak ada wallet.dat di electrum, [dot]dat hanya untuk core. Nanti kebingungan nyari ekstensi file .dat yang memang tidak ada.

di electrum ekstensinya hanya berupa file, adanya di /data/org.electrum.electrum/files/data/wallets di android.

Jangan biasakan kirim-kirim/ekspor file wallet via email, messenger, dll. jangan pakai cara lama seperti token/eth dll.
Saran saya, Kalau ada Laptop lebih baik pakai electrum di sana saja.

Om Kebetulan saya baru saja download Android Walletnya.

1. Apakah Setelah Selesai Download dan Run Aplikasi, Tidak ada yang perlu di setting lagi?

2. Kalau Mau Lihat Wallet Itu Addresses Kan Ya Om?

3. Wallet.dat kita bisa kita export dari Android dan import di Electrum Desktop Windows?

Untuk seed Segwit (bech32) saya cek di https://iancoleman.io/bip39/ compatible,

Awalnya ane kira bech32 juga ga kompatibel. Agak menarik juga sih kenapa ga sekalian dibuat kompatibel keduanya, atau emang dari dulu cuma legacy aja yang ga sesuai bip39? Seingat ane yang bech juga beda ketika buat wallet baru dulu.

~

Jika agan mengaktifkan backup wallet, maka kemungkinan wallet.dat nya bisa digunakan ke electrum versi deskop. Tapi ane pikir agan masih bisa menyimpan beberapa privatekey dari address yang paling agan sukai untuk digunakan di versi deskop. Tapi bagusnya ya wallet.dat nya saja sekalian.

1. Apakah Setelah Selesai Download dan Run Aplikasi, Tidak ada yang perlu di setting lagi?

2. Kalau Mau Lihat Wallet Itu Addresses Kan Ya Om?

3. Wallet.dat kita bisa kita export dari Android dan import di Electrum Desktop Windows?

Maaf pertanyaan noob om, saya masih banyak belum menegerti hehehe.

-snip- nampaknya seed yang dibuat di versi terbaru ini masih belum BIP39 compatible. Semoga pada tahu hal ini sebelum bikin seed baru.

# Release 4.1.0 - Kangaroo (March 30, 2021)

This version is our second major release with support for the
Lightning Network. While our initial Lightning release was mostly
about implementing the protocol, this release brings features that are
specifically aimed at keeping Electrum lightweight and trustless,
while avoiding single points of failure. Most of the features listed
below are user-visible.
 * The wallet creation wizard no longer asks for a seed type, and
   creates segwit wallets with bech32 addresses. Older seed types can
   still be created with the command line.
 * Paid invoices (both incoming and outgoing) are automatically
   removed from the send/receive lists of the GUI (one confirmation is
   needed for onchain invoices). Once removed from the list, invoice
   details can still be accessed from the transaction history. In Qt,
   invoice lists have been renamed to 'Sending queue' and 'Receiving
   queue'.
 * Lightning:
    - recoverable channels (see below)
    - trampoline payments (see below)
    - support multi-part-payment
    - support upfront-shutdown-script
 * Recoverable channels (option):
   - Recovery data is added to the channel funding transaction using
     an OP_RETURN. This makes it possible to recover a static backup
     of the channel from the wallet seed. Please note that static
     backups only allow users to request a force-close of the channel
     with the remote node, so that funds not locked in HTLCs can be
     recovered. This assumes that the remote node is still online, did
     not lose its data, and accepts to force close the channel.
   - This option is only available for standard wallets with an
     Electrum seed. It is not available for hardware wallets, because
     it requires a deterministic derivation of the nodeID. It is also
     not available in watching-only wallets, for the same reason. If a
     wallet can have recoverable channels but has an old nodeID, users
     who want to use that feature need to close all their existing
     channels, and to restore their wallet from seed.
   - Channel recovery data uses 20 bytes (16 bytes of the remote
     NodeID plus 4 magic bytes) and is encrypted so that only the
     wallet that owns it can decrypt it. However, blockchain analysis
     will be able to tell that the transaction was probably created by
     Electrum.
   - If the 'use recoverable channels' option is enabled, other nodes
     cannot open a channel to Electrum.
   - If a channel is force-closed, the information in the on-chain
     backup is not sufficient to retrieve the funds in the to_local
     output, in case the wallet is lost in a boating accident before
     expiration of the CSV delay. For that reason, an additional
     backup is presented to the user if they force-close a channel.
 * Trampoline routing (option): Trampoline is a solution that allows
   light clients to delegate path-finding on the Lightning Network, so
   that they do not have to download the entire network
   graph. Trampoline routing was originally proposed by Bastien
   Teinturier and is used in the Phoenix wallet. Here is how
   Trampoline works in Electrum:
   - Trampoline is enabled by default, in order to prevent unwanted
     download of the network gossip. If trampoline is disabled, the
     gossip will be downloaded, regardless of the existence of
     channels.
   - Because there is no discovery mechanism for trampoline nodes, the
     list of available trampolines is hardcoded in the client (it will
     remain so until support for trampoline routing is announced in
     gossip). 3 trampoline nodes are currently available on mainnet:
     ACINQ, Electrum and Hodlister.
   - If Trampoline is enabled:
      - payments use trampoline routing.
      - gossip is disabled.
      - the wallet can only open channels with trampoline nodes.
      - pre-existing channels with non-trampoline nodes are frozen for
        sending.
   - There are two types of trampoline payments: legacy and trampoline
     end-to-end. Legacy payments are possible with any receiver, but
     they offer less privacy than end-to-end trampoline
     payments. Electrum decides whether to perform legacy or
     end-to-end based on the features in the invoice:
       - OPTION_TRAMPOLINE_ROUTING_OPT (bit 25) for Electrum
       - OPTION_TRAMPOLINE_ROUTING_OPT_ECLAIR (bit 51) for Eclair/Phoenix
   - When performing a legacy payment, Electrum will add a second
     trampoline node to the route in order to protect the privacy of
     the payer and payee. It will fall back to a single trampoline if
     the two-trampoline strategy has failed for all trampolines.
     (Note: two-trampoline payments are currently not possible if the
     first trampoline is the ACINQ node, and is disabled for that
     node.)
   - Similar to Phoenix, the fee and CLTV delay are found by
     trial-and-error. If there is a second trampoline in the route, we
     use the same fee/CLTV for both. This trial-and-error is
     temporary; the final specification should add fee information in
     the failure messages, so that we will be able to better fine-tune
     trampoline fees.
 * Qt: The increase fee dialog now has advanced options, and offers
   the choice between different RBF strategies.
 * Watchtowers: The 'use_local_watchtower' feature is deprecated, and
   it has been removed from the Qt GUI. The 'use_remote_watchtower'
   setting has been renamed to 'use_watchtower'.
 * Password unification (Android only): When the Android app is
   started, the entered password is checked against all wallets in
   the directory. If the test passes:
    - all wallets are encrypted
    - new wallets will use the unified password
    - password updates are performed on all wallets
   Whether the password is unified can be seen in the GUI: In the
   'Settings' dialog, the description for the password setting is
   'Change password for this wallet' if the password is not unified,
   and becomes 'Change password' if password is unified.
 * Submarine swaps are now available on kivy/android.
 * Android PIN reset: If the password is unified, the PIN can be reset
   by providing the password.
 * Android: on-chain fees have been removed from the settings
   dialog. Instead, the fee slider is shown to the user everytime an
   on-chain transaction will be performed (sending a payment, opening
   a channel, initiating a submarine swap)
 * BIP-0350: use bech32m for witness version 1+ addresses (4315fa43).
   We have supported sending to any witness version since Electrum
   3.0, using BIP-0173 (bech32) addresses. BIP-0350 makes a breaking
   change in address encoding, and recommends using a new encoding
   (bech32m) for sending to witness version 1 and later.
 * Block explorer: allow setting a custom URL in Qt GUI (#6965)

Mungkin cuma work di testnet saja Om dan tidak work di transaksi realnya. Tapi tidak apa-apa Om, besok rencananya mau coba langsung saja di real transaksi saat TX belum di konfirmasi dan juga menggunakan fee yang sama dengan TX pertama. Semoga saja tidak ada masalah.

Baik Om, besok rencananya kalau sempat mau test langsung saja dengan fee yang sama.

Testnet dibuat sama dengan aslinya memang untuk uji coba, jadi kalaupun ada beda, tipis. akan tapi karena jaringan testnet sedikit, jadi walaupun pakai fee sama dengan real tentu akan cepat terkonfirmasi di jaringan testnet.

Mungkin cuma work di testnet saja Om dan tidak work di transaksi realnya. Tapi tidak apa-apa Om, besok rencananya mau coba langsung saja di real transaksi saat TX belum di konfirmasi dan juga menggunakan fee yang sama dengan TX pertama. Semoga saja tidak ada masalah.

besok rencananya mau coba langsung saja di real transaksi saat TX belum di konfirmasi dan juga menggunakan fee yang sama dengan TX pertama. Semoga saja tidak ada masalah.

Bahkan jika menggunakan fee transaksi yang sama/hampir setara, bisa saja ketika TX pertama mendapat 1 konfirmasi, maka TX kedua mendapatkan konfirmasi yang sama, dan bisa saja kedua TX tersebut disertakan pada block yang sama; Sebagaimana contoh transaksi yang saya buat sebelumnya di atas, jika di periksa keduanya disertakan pada block yang sama.

~snip

Berarti selama TX nya tidak berubah sampai terkonfirmasi maka TX kedua ini akan berhasil juga. Kalau TX pertama berubah atau dibatalkan oleh fitur double spend maka secara otomatis TX kedua akan gagal. Baik Om, ane ngerti sekarang dan terimakasih juga karena sudah mau mengujinya Om.

Bahkan jika menggunakan fee transaksi yang sama/hampir setara, bisa saja ketika TX pertama mendapat 1 konfirmasi, maka TX kedua mendapatkan konfirmasi yang sama, dan bisa saja kedua TX tersebut disertakan pada block yang sama

-snip- selama TX pertama tidak berubah atau diganti dengan TX baru menggunakan fitur Cancel Double Spend maka TX kedua akan dikonfirmasi yang kecepatannya tergantung pada fee yang digunakan pengirim.

~snip

~snip

Mungkin agan-agan pernah melakukannya, jadi ane ingin tahu apakah transaksi itu mendapatkan konfirmasi atau tidak, soalnya kemaren lupa ane periksa txid tersebut.