Options in life are important. How about getting our money out of a wallet, as well as putting money into it? <p><center> <a href="https://pixabay.com/illustrations/bitcoin-lightning-thunderstorm-7678816/"><img src="https://images.hive.blog/700x0/https://images.hive.blog/DQmbdpq58v6Mu7QzKEufnjyKJB2CkvTseaBhPL1SsUbZz9g/bitcoin-7678816_1280[1].jpg" target="_blank"></a><br> <sup>Source: Creator <a href="https://pixabay.com/users/midjourney-32375630/" target="_blank">MidJourney</a> on <a href="https://pixabay.com/illustrations/bitcoin-lightning-thunderstorm-7678816/" target="_blank">Pixabay</a> </sup> </center></p> It might be important! Hahaha ... Published inside this new community's UI, I would like to provide some details to what is currently a challenge. Moving BTC back and forth, from Wallet A to Wallet B. <p><center> <img src="https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png"> </center></p> <h2>L1: Native Segwit</h2> As it was the original crypto, Bitcoin has a long history of continuous improvement. One of the critical aspects of these improvements was the address type used. And the resulting fee to the user. Segregated Witness, i.e. SegWit, is one of these address types. <a href="https://bitcoin.stackexchange.com/questions/93013/are-all-three-bitcoin-address-types-interoperable-legacy-segwit-native-segwit" target="_blank">Native Segwit or Bech32</a> addresses are generally considered the current universal standard and begin with 'bc1.' They offer better efficiencies and lower fees than older address types. For the purposes of the One Bitcoin Club community, in following instructions to set-up an Xverse wallet address, we will almost certainly end up with a Native Segwit address. A key is this is an L1 issue, i.e. associated with the Bitcoin blockchain itself. And, therefore, Native Segwit addresses are compatible with other L1 address types. <p><center> <img src="https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png"> </center></p> <h2>L2: Lightning</h2> An enormous problem associated with Bitcoin's architecture is its inflexibility to scale up to handle large numbers of transactions. In handling relatively simple buy-and-HODL investments, this is not an insurmountable problem, as we can see over its long history. Handling buy-and-sell purchases? A big problem. One which the L2 layer referred to as <a href="https://lightningaddress.com/" target="_blank">Lightning</a> was created to solve. It comfortably handles large numbers of micropayment amounts and does so via the use of an address that looks much like an email address versus a cryptographic address. For the purposes of the One Bitcoin Club community, @brianoflondon has created the V4V.app with its Lightning address and interoperability with the Hive blockchain. It is through this address that members of the community will receive any Sats for contributing content to it. <ul><ul> <li><sup> Note: You simply log in to the <a href="https://v4v.app" target="_blank">V4V.app</a> website with Hive Keychain. Then copy and paste the address found under the Receive link into the associated Settings field on your One Bitcoin Club account. </sup></li> </ul></ul> <p><center> <img src="https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png"> </center></p> <h2>Lightning <div class="phishy"><≠></div> Native Segwit<div class="phishy">?</div></h2> One is an L2 address and one is an L1 address. Think HIVE and SWAP.HIVE, for those familiar with the L2 tokens on the L2 Hive Engine blockchain. <p><h4><center> Want to <div class="phishy"><strong><em>transfer</em></strong></div> BTC <br> from V4V.app to Xverse wallet? <br> </center></h4></p> Are they compatible? Certainly the answer has to be considered as at least <code>not <strong><em>easily compatible</em></strong></code>. Some posts found indicate that they are completely incompatible. One thing seemed obvious to me, in searching for an answer. It does not appear to be a trivial challenge. The closest content I could find: <blockquote> <em>"yes you can import that seed into a bitcoin wallet. by finding the LN seed in the LN wallet and copying it over. but some LN nodes methods of backup/access to that seed is not easy"</em><br><br>[<a href="https://bitcointalk.org/index.php?topic=5421782.0" target="_blank">Source</a>: Bitcointalk.org] </blockquote> If there is any such route via our V4V.app wallet address, I did not find it. <p><center>________________________</center></p> <h4><div class="phishy"><strong><em>One</em></strong></div> Solution! For now.</h4> Not claiming to be any sort of an expert on the topic, but with experience in the broader crypto world outside the Hive blockchain, I was happy to find <code>my <strong><em>"Swiss Army Knife"</em></strong> solution</code> worked: <p><center> <a href="https://swapspace.co/exchange/step1?to=btc&toNetwork=btc&from=btc&fromNetwork=lightning&amount=0.001&direction=direct"> <img src="https://images.hive.blog/700x0/https://images.hive.blog/DQmWG9Gdf1ipQE7D8rurNYTuyVJBp9vujKVXb1q68Uo268C/image.png" target="_blank"> </a><br><sup> Source: BTC Lightning to Native Segwit exchange on <a href="https://swapspace.co/exchange/step1?to=btc&toNetwork=btc&from=btc&fromNetwork=lightning&amount=0.001&direction=direct" target="_blank">SwapSpace</a> </sup><br> </center></p> <u>Note</u>: <ul> <li>The minimum is ~ 0.00015 BTC, which is about $12.00 USD at today's prices of ~ $80,000 / BTC. The fee would be a very steep ~ 12.1%.</li><br> <li>Upping to 0.001 BTC, which is about $80.00 USD at today's prices, the fee would be a bit more reasonable ! 2.2%.<</li><br> <li>In either case, the transaction time is a remarkable ~ 5 minutes. With BTC, that is hard to beat.</li> </ul> <p><h4><center> Usual caveat: <br> <div class="phishy">NFA. DYOR. </div> </center></h4></p> <p><center>________________________</center></p> There seems to be a lot going on at all times around the Hive blockchain. Perhaps the <a href="https://vsc.eco/" target="_blank">VSC Network</a> has a solution for this challenge already in the works. If there is not another one, unknown to me, already in place. I will now follow the @vsc.network account, so I will see any updates in my feed. The last one was in November, so maybe soon? <p><center> <img src="https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png"> </center></p> Closing and keeping our eye on the future ... <p><center> <a href="https://pixabay.com/photos/bitcoin-cryptocurrency-blockchain-4186236/"><img src="https://images.hive.blog/400x0/https://images.hive.blog/DQmYyYEK9HPhB2PsnDJmnUBsFmLU29yhA8ChGk9bSQc4h7w/bitcoin-4186236_1280[1].jpg" target="_blank"></a><br> <sup>Source: My original post titled "<a href="https://peakd.com/hive-125568/@quark.top/problem-or-opportunity-mvp-and-joining-the-one-btc-club" target="_blank">Problem or Opportunity? MVP and Joining the One BTC Club</a>" </sup> </center></p> ... I have no doubt this issue will be resolved soon, if it is not relatively easily resolved already. Somewhere. In some way. <p><center>________________________</center></p> As the Community Leaders begin to join in with their contributions to One Bitcoin Club's content, I am looking forward to what they have to share. In time, I am sure questions like these will be fully addressed. What questions have you run into, in thinking about or joining the One Bitcoin Club community? Best wishes, until we meet again, QT <center><h2> 👋❤️👋 </h2></center> <p><center> <img src="https://images.hive.blog/500x0/https://images.hive.blog/DQmT2SxtrtCa1BtrWugjqwGyd4gPigLSueVC4yePTgEYAnr/QT_Brand_Closing.png"> </center></p> <p><center> <a href="https://pixabay.com/vectors/bitcoin-digital-currency-4130319/"><img src="https://images.hive.blog/300x0/https://images.hive.blog/DQmYpDYrFzaP3k5XuBqCh2RBGNKzbQ33U9oA78KyBd48jka/bitcoin-4130319_1280[1].png" target="_blank"></a><br> <sup>Source: Creator <a href="https://pixabay.com/users/gdj-1086657/" target="_blank">GDJ</a> on <a href="https://pixabay.com/vectors/bitcoin-digital-currency-4130319/" target="_blank">Pixabay</a> </sup> </center></p> <br> <p><center>________________________</center></p> <p><center> <h4>🤝 <a href="https://peakd.com/introduceyourself/@quark.top/engespdeu-introduction-qt-enters-the-hive-portal" target="_blank">Partnership Pledge!</a> 🤝</h4> •  10% of Post Payout to Comments<br> •  1 <a href="https://peakd.com/hive-140084/@freecompliments/an-updated-explanation-of-hsbi-a-wonderful-service-for-those-who-plan-to-stick-around-hive-for-a-long-time-26q" target="_blank">HSBI</a> to the Best Comment </center></p> <p><center>________________________</center></p> <p><center> <h4>🥲 Pledge <div class="phishy"><em>Not</em></div> Honored! 🥲</h4> •  <b><em>Not</em></b></div> due to a change of heart.<br>•  No comment in time. Nothing to upvote. </center></p> <br> <p><center>________________________</center></p> <center><h3>Edit (UI Issues): 14 Mar 2025</h3></center> <ul> <li>After making devs <a href="https://peakd.com/hive-125568/@quark.top/re-breakaway-dev-ssz3gj" target="_blank">aware</a> that my first <a href="https://onebitcoinclub.org/hive-125568/@quark.top/yes-logged-into-the-one" target="_blank">post</a>, using the One Bitcoin Club UI, had no lead image, in the community view of all posts, it has just happened again.  In both cases, the lead image does not appear on PeakD's UI community view either.</li> <li>This edit is intentionally being published with PeakD's UI, to see if the lead image reappears, in the update.  I have never experienced this issue before now and am attempting to help find a solution.</li> <li>Publishing this edit did not help. If by any chance, you are able to see my lead image, in the community view of all posts, from whichever UI you might be using, I would appreciate you letting me know.</li> </ul>
author | quark.top | ||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
permlink | bitcoin-addresses-lightning-v4v-app | ||||||||||||||||||
category | hive-125568 | ||||||||||||||||||
json_metadata | {"app":"ecency/3.0.22-vision","format":"markdown","image":["https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png","https://images.hive.blog/700x0/https://images.hive.blog/DQmbdpq58v6Mu7QzKEufnjyKJB2CkvTseaBhPL1SsUbZz9g/bitcoin-7678816_1280[1].jpg","https://images.hive.blog/700x0/https://images.hive.blog/DQmWG9Gdf1ipQE7D8rurNYTuyVJBp9vujKVXb1q68Uo268C/image.png","https://images.hive.blog/400x0/https://images.hive.blog/DQmYyYEK9HPhB2PsnDJmnUBsFmLU29yhA8ChGk9bSQc4h7w/bitcoin-4186236_1280[1].jpg","https://images.hive.blog/500x0/https://images.hive.blog/DQmT2SxtrtCa1BtrWugjqwGyd4gPigLSueVC4yePTgEYAnr/QT_Brand_Closing.png","https://images.hive.blog/300x0/https://images.hive.blog/DQmYpDYrFzaP3k5XuBqCh2RBGNKzbQ33U9oA78KyBd48jka/bitcoin-4130319_1280[1].png"],"links":["https://pixabay.com/illustrations/bitcoin-lightning-thunderstorm-7678816/","https://images.hive.blog/700x0/https://images.hive.blog/DQmbdpq58v6Mu7QzKEufnjyKJB2CkvTseaBhPL1SsUbZz9g/bitcoin-7678816_1280","https://pixabay.com/users/midjourney-32375630/","https://pixabay.com/illustrations/bitcoin-lightning-thunderstorm-7678816/","https://bitcoin.stackexchange.com/questions/93013/are-all-three-bitcoin-address-types-interoperable-legacy-segwit-native-segwit","https://lightningaddress.com/","https://v4v.app","https://bitcointalk.org/index.php?topic=5421782.0","https://swapspace.co/exchange/step1?to=btc&toNetwork=btc&from=btc&fromNetwork=lightning&amount=0.001&direction=direct","https://swapspace.co/exchange/step1?to=btc&toNetwork=btc&from=btc&fromNetwork=lightning&amount=0.001&direction=direct"],"tags":["bitcoin","btc","onebitcoinclub","v4vapp","investing","saving","saturdaysavers","silverbloggers","proofofbrain","hive-125568"],"thumbnails":["https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png","https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png","https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png","https://images.hive.blog/700x0/https://images.hive.blog/DQmWG9Gdf1ipQE7D8rurNYTuyVJBp9vujKVXb1q68Uo268C/image.png","https://images.hive.blog/300x0/https://images.hive.blog/DQmaUpjP6piz9ZftABqrARagF2JbVMZQvxT6S4G9VZUGwRv/QT_Divider.png","https://images.hive.blog/500x0/https://images.hive.blog/DQmT2SxtrtCa1BtrWugjqwGyd4gPigLSueVC4yePTgEYAnr/QT_Brand_Closing.png"],"users":["brianoflondon","vsc.network","quark.top","freecompliments"]} | ||||||||||||||||||
created | 2025-03-14 13:43:06 | ||||||||||||||||||
last_update | 2025-03-31 20:16:21 | ||||||||||||||||||
depth | 0 | ||||||||||||||||||
children | 7 | ||||||||||||||||||
last_payout | 2025-03-21 13:43:06 | ||||||||||||||||||
cashout_time | 1969-12-31 23:59:59 | ||||||||||||||||||
total_payout_value | 0.000 HBD | ||||||||||||||||||
curator_payout_value | 2.841 HBD | ||||||||||||||||||
pending_payout_value | 0.000 HBD | ||||||||||||||||||
promoted | 0.000 HBD | ||||||||||||||||||
body_length | 10,232 | ||||||||||||||||||
author_reputation | 6,255,537,028,767 | ||||||||||||||||||
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" | ||||||||||||||||||
beneficiaries |
| ||||||||||||||||||
max_accepted_payout | 1,000,000.000 HBD | ||||||||||||||||||
percent_hbd | 10,000 | ||||||||||||||||||
post_id | 141,427,688 | ||||||||||||||||||
net_rshares | 16,840,084,030,931 | ||||||||||||||||||
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
randomblock1 | 0 | 1,514,093,609 | 20% | ||
joeyarnoldvn | 0 | 464,361,241 | 1.47% | ||
minismallholding | 0 | 150,621,672,233 | 20% | ||
izzydawn | 0 | 5,256,675,692 | 20% | ||
upme | 0 | 12,575,304,506 | 20% | ||
cryptkeeper17 | 0 | 927,403,128 | 40% | ||
realtreebivvy | 0 | 3,174,846,116 | 20% | ||
life-relearnt | 0 | 4,178,148,567 | 20% | ||
sbi5 | 0 | 49,031,510,122 | 4.04% | ||
apshamilton | 0 | 871,223,867,820 | 50% | ||
hamismsf | 0 | 282,709,477,532 | 50% | ||
smartvote | 0 | 83,119,320,813 | 3.8% | ||
yaelg | 0 | 23,998,283,582 | 45% | ||
brianoflondon | 0 | 9,058,237,137,230 | 100% | ||
jpbliberty | 0 | 27,656,805,635 | 100% | ||
sbi-tokens | 0 | 596,557,510 | 0.7% | ||
replicantua | 0 | 951,434,754 | 22% | ||
reward.app | 0 | 161,672,563,379 | 40% | ||
sevenoh-fiveoh | 0 | 9,510,288,816 | 20% | ||
zwhammer | 0 | 1,197,195,409 | 50% | ||
hivehydra | 0 | 886,643,032 | 90% | ||
podping | 0 | 763,653,477,553 | 100% | ||
cryptoccshow | 0 | 1,400,214,004 | 50% | ||
iproto | 0 | 19,860,682,149 | 50% | ||
fikif | 0 | 3,573,837,524 | 40% | ||
koussbar | 0 | 953,589,533 | 40% | ||
madame-cyntaia | 0 | 2,616,331,768 | 24% | ||
acgalarza | 0 | 406,636,318,582 | 100% | ||
cryptoluz | 0 | 2,129,925,326 | 100% | ||
samuraiscam | 0 | 2,167,068,855 | 40% | ||
somecallmejake | 0 | 4,887,588,994,911 | 30.3% |
@quark.top, I'm refunding 0.349 HIVE and 0.085 HBD, because there are no comments to reward.
author | commentrewarder |
---|---|
permlink | re-quarktop-bitcoin-addresses-lightning-v4v-app14724 |
category | hive-125568 |
json_metadata | {"app":"CommentRewarder"} |
created | 2025-03-17 13:43:18 |
last_update | 2025-03-21 13:43:27 |
depth | 1 |
children | 0 |
last_payout | 2025-03-24 13:43:18 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 92 |
author_reputation | 52,275,539,527,009 |
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 141,489,941 |
net_rshares | 0 |
Congratulations @quark.top! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s) <table><tr><td><img src="https://images.hive.blog/60x70/https://hivebuzz.me/@quark.top/upvoted.png?202503141832"></td><td>You received more than 1250 upvotes.<br>Your next target is to reach 1500 upvotes.</td></tr> </table> <sub>_You can view your badges on [your board](https://hivebuzz.me/@quark.top) and compare yourself to others in the [Ranking](https://hivebuzz.me/ranking)_</sub> <sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>
author | hivebuzz |
---|---|
permlink | notify-1741977513 |
category | hive-125568 |
json_metadata | {"image":["https://hivebuzz.me/notify.t6.png"]} |
created | 2025-03-14 18:38:33 |
last_update | 2025-03-14 18:38:33 |
depth | 1 |
children | 0 |
last_payout | 2025-03-21 18:38:33 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 631 |
author_reputation | 370,071,659,156,880 |
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 141,433,602 |
net_rshares | 0 |
I was the problem I run into when I tried to send Sats to Xverse believing that the address to receive assets in Xverse was going to accept Satoshi Lightning. It was not possible, so I used Binance to complete the transaction using segwit sending protocol. Storing Sats on Xverse is not going to motivate people since I can easily transfer Sats from Binance to wallet of Satoshi using Lightning network and from wallet of satoshi to V4V app. I have a question, is possible to use our V4Vapp address on all lightning wallet transaction? It was not possible to send Satoshi from the app Fountain to V4V app wallet using lightning network, I had to go through wallet of Satoshi.
author | rogerlabanane |
---|---|
permlink | re-quarktop-2025317t82843343z |
category | hive-125568 |
json_metadata | {"tags":["bitcoin","btc","onebitcoinclub","v4vapp","investing","saving","saturdaysavers","silverbloggers","proofofbrain","hive-125568"],"app":"ecency/3.0.22-vision","format":"markdown+html"} |
created | 2025-03-17 07:28:45 |
last_update | 2025-03-17 07:28:45 |
depth | 1 |
children | 1 |
last_payout | 2025-03-24 07:28:45 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.014 HBD |
curator_payout_value | 0.013 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 676 |
author_reputation | 8,104,177,220,532 |
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 141,484,017 |
net_rshares | 87,854,914,027 |
author_curate_reward | "" |
voter | weight | wgt% | rshares | pct | time |
---|---|---|---|---|---|
dustsweeper | 0 | 78,652,839,160 | 9.57% | ||
quark.top | 0 | 9,202,074,867 | 100% |
Yes, CEXes like Binance can handle it. Aggregators, like <a href="https://swapspace.co/?to=eth&toNetwork=eth&from=btc&fromNetwork=btc&amount=0.1&direction=direct" target="_blank">SwapSpace</a> I mentioned, utilize that and other options, without the need to actually have an account in any of them. My personal hope is there will be future DEX solutions, which do not yet exist, at least as far as I am aware.
author | quark.top |
---|---|
permlink | re-rogerlabanane-st9z9h |
category | hive-125568 |
json_metadata | {"tags":["hive-125568"],"app":"peakd/2025.2.3"} |
created | 2025-03-17 16:03:33 |
last_update | 2025-03-17 16:03:33 |
depth | 2 |
children | 0 |
last_payout | 2025-03-24 16:03:33 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 411 |
author_reputation | 6,255,537,028,767 |
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 141,492,903 |
net_rshares | 0 |
Are you centering the lead image? I remember in the Inleo UI that didn't work and perhaps it doesn't here either.
author | tengolotodo |
---|---|
permlink | re-quarktop-2025319t155441701z |
category | hive-125568 |
json_metadata | {"tags":["bitcoin","btc","onebitcoinclub","v4vapp","investing","saving","saturdaysavers","silverbloggers","proofofbrain","hive-125568"],"app":"ecency/4.0.3-vision","format":"markdown+html"} |
created | 2025-03-19 15:54:42 |
last_update | 2025-03-19 15:54:42 |
depth | 1 |
children | 2 |
last_payout | 2025-03-26 15:54:42 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 114 |
author_reputation | 810,927,897,604,619 |
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 141,537,706 |
net_rshares | 0 |
Thank you for the input, @tengolotodo. While possible, I doubt that is the case. To answer your question, I always center my lead image. And PeakD handles it just fine. To your point, if that was the issue, I would expect my post to still display just fine, when viewing it in PeakD's view of the community. As stated above, however, it does not. Also, once opened, both UI's show the lead image just fine. How is that possible? More precisely, why does it appear fine when actually opening the post to read it vs. the preview of it in the (any!) community listing? 🤷♂️ Whatever it is, these are the types of issues devs typically like having brought to their attention, as they are best equipped to address them.
author | quark.top |
---|---|
permlink | re-tengolotodo-stdqll |
category | hive-125568 |
json_metadata | {"tags":["hive-125568"],"app":"peakd/2025.3.4"} |
created | 2025-03-19 16:46:51 |
last_update | 2025-03-19 16:46:51 |
depth | 2 |
children | 1 |
last_payout | 2025-03-26 16:46:51 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 722 |
author_reputation | 6,255,537,028,767 |
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 141,538,967 |
net_rshares | 0 |
Well I guess it depends what front end the bitcoin club is based on. Well I hope you get your answers.
author | tengolotodo |
---|---|
permlink | re-quarktop-2025319t193221200z |
category | hive-125568 |
json_metadata | {"tags":["hive-125568"],"app":"ecency/4.0.3-vision","format":"markdown+html"} |
created | 2025-03-19 19:32:21 |
last_update | 2025-03-19 19:32:21 |
depth | 3 |
children | 0 |
last_payout | 2025-03-26 19:32:21 |
cashout_time | 1969-12-31 23:59:59 |
total_payout_value | 0.000 HBD |
curator_payout_value | 0.000 HBD |
pending_payout_value | 0.000 HBD |
promoted | 0.000 HBD |
body_length | 103 |
author_reputation | 810,927,897,604,619 |
root_title | "Bitcoin Addresses: Lightning(v4v.app) <≠> Native Segwit (Xverse)?" |
beneficiaries | [] |
max_accepted_payout | 1,000,000.000 HBD |
percent_hbd | 10,000 |
post_id | 141,541,995 |
net_rshares | 0 |