Is there a way to switch off this feature in Ledger Nano S? It has now created 5 addresses in my wallet and there is no option to choose a specific sending address as it chooses that on its own. Pretty much all wallets exhibit this behaviour by default nowadays... it's to avoid "address re-use" ( https://en.bitcoin.it/wiki/Address_reuse) Some addresses contain less than 0.01 btc which may increase the required network fee.
Note that having your coins spread across multiple addresses does NOT affect the fees you are going to pay if you want to spend. It is mostly effected by the total number of UTXOs. If you send multiple individual transactions to one address, the inputs are not "combined", they are still regarded as separate UTXOs. So, 100 inputs spread across 100 addresses will generate the same sized transaction ( and require same fee) as 100 inputs in 1 address... as they're still 100 inputs! The only way to combine them all into 1, is to send ALL your money to yourself in a single transaction to consolidate them all into 1 single UTXO... which actually only really saves you money if the network goes crazy, the mempool floods and fees spike to like 100 sats/byte+ again. You can read about consolidation here: https://bitcointalk.org/index.php?topic=2848987.0There is no such option in Ledger Nano. I checked all options in Settings for that means it will go on for each transaction and I will need to login to my account to know my real balance. Will need to use Electrum to send from a specific address and avoiding this change address feature.
So, you're just wanting to be able to monitor a single address and continually re-use it?  Why? It's bad for your privacy and the privacy of people you transact with (read the address re-use link above). In any case, using Electrum to monitor a single address is no different to opening Ledger Live and viewing your balance... does it really matter if your X BTC is spread across 5 different addresses? |
|
|
|
DON'T use this website or any versions of Armory from it. It is very old and outdated... the NEW Armory website with the most up to date versions is: https://btcarmory.com/I just downloaded armory made a wallet but i cant seem to figure out how to make the scan happen so i can go online
Let's start with the very basics... do you have the latest version of Bitcoin Core (0.19.0.1) installed, running and FULLY synced? If not, Armory will NOT be able to function properly. It absolutely requires Bitcoin Core and it's blockchain data to be able to function. Also, make sure you are running Armory 0.96.5... available from: https://btcarmory.com/Older versions don't play well with latest versions of Bitcoin Core. |
|
|
|
1. For those bitcoin services website, like bitcoin exchanges, how are they able to generate unique bitcoin address for each users? Do they use a BIP wallet to generate those bitcoin address, or some other methods?
Yes  It's impossible to know as most don't openly advertise how they handle these types of things. I'm sure there are websites that are using "HD" wallets to generate keys from seeds, and others that simply use the old "RNG" method to just randomly generate keys as required. Others probably use hardware wallets etc. How long is a piece of string? 2. Do they store those bitcoin address on their public web server? I am thinking that when you visit their website, their back-end will surely get your assigned bitcoin address from somewhere in their system, so they can check for the balance, so I am guessing bitcoin address are stored on their webserver. Will storing bitcoin address on webserver pose a security threat?
Addresses aren't really a "security threat" as such... they are after all, ALL published within the blockchain data for everyone to see when they receive coins. I would assume that they are storing their address list somewhere... whether that is on their public webserver or not is probably more a function of performance and latency than anything else. 3. Likewise, do they store private keys of those addresses on webserver? If no due to security concerns, then how are users able to withdraw their bitcoin from the website, especially since the private keys are in cold-wallet and thus they are not connected to the public webserver?
If they are storing private keys on a webserver, they are pretty stupid. Private keys are called "private" for a reason. Putting them anywhere near a public facing server is a recipe for disaster. Users don't generally create a transaction, sign it and then broadcast it... they will create a "withdrawal request", which is then processed by the system. As long as the system has access to the appropriate keys, that's all that really matters. 4. Most website will have their own bitcoin addresses to pool in all the funds deposited from the users' bitcoin address. This addresses are then used for user's withdrawals. How are they able to check which user's public address have funds in it, so they can transfer the funds to their own address, especially if they have so many users? Also, how they able to handle user's withdrawal in this case, assuming the private keys of their own pool addresses are stored offline? What if users require instant withdrawal?
I would think that most of the sites don't do it like this. Instead, each user will have an account (SomeUser) and some associated Database values (like AccountBalance, DepositAddress etc). Each DepositAddress is assigned to the user either semi-permanently (and re-used for each deposit, I've seen a couple of gambling sites in particular that do this) or they automatically get assigned a new DepositAddress whenever the current one is "used" and has received funds for the first time (most exchanges seem to do this). SomeUser then logs in, and clicks on the "deposit BTC" link... they are presented with the DepositAddress that is currently linked in the backend database with their SomeUser account. SomeUser then sends some BTC from their external wallet to DepositAddress. Custom software (or maybe a modified version of Bitcoin Core etc), monitoring the sites wallet addresses, detects a transaction to DepositAddress. Once that transaction is confirmed, the "AccountBalance" for SomeUser is then incremented by value of the transaction. When a user wants to withdraw, they issue a request to withdraw a certain amount of BTC (AmountRequested) to a certain address (WithdrawAddress)... The system simply checks that SomeUser.AccountBalance >= AmountRequested and that WithdrawAddress is a "valid" BTC address. If they are, then the backend can either immediately create a transaction that sends AmountRequest to WithdrawAddress using whatever hotwallet funds they have (basically using funds from ANY address(es) in the sites hot wallet)... or, if they're a site that likes to batch transactions, they can add the request to the queue. At this point, SomeUser.AccountBalance will be decremented by AmountRequested (+fee )... and most likely a "pending" transaction entry will be added to their account history etc. Scheduled tasks could be used to shift funds from hot wallet deposit addresses to cold storage... or you could simply do it whenever hot wallet balance exceeds a certain threshold. Likewise the refilling of hotwallet is likely done when the balance falls below a certain threshold to ensure enough funds are available to satisfy "instant withdrawal". Obviously there is a lot of room for debate as to which is the "best" method for these types of systems... or what is an "acceptable" amount to hold in a hot wallet before shifting to cold... or what is minimum amount required in hot wallet. It will be very much site specific and vary according to the level of risk the site is willing to carry, what their incoming/outgoing transaction numbers/values are etc. Note that the above is a mixture of guesswork/assumption and casual conversation with site owners on how they handle things in "general terms" without low level specifics etc. |
|
|
|
I am not sure but I think electrum send address per tx even with this option No, as Theb stated, Electrum definitely allows "PayToMany" and putting multiple recipients in one transaction... NOTE: done with TestNet, but the MainNet version works the same Sending four different amounts to four different addresses:  Transaction preview showing four external recipients + 1 change address:  Final transaction showing on BlockExplorer:  |
|
|
|
In summary, Ledger Live will ONLY let you add the account type(s) where the last account of that type is already "used".
This is some fucked way to generate a new address. Is there any reason why they do this? No. It isn't about generating new "addresses"... it is about generating new " accounts" within Ledger Live. An "account" in Ledger Live is basically the same thing as a "wallet file" in Electrum. It only allows you to generate one type of address... so your wallet file in Electrum will be either Nested Segwit ("3")... or Native Segwit ("bc1") addresses... you can't mix them. And just like Electrum... each account in Ledger Live lets you have multiple addresses... you just open the account in Ledger Live, click "receive" and it will provide you with the next unused address from that account. Ledger... for whatever reason decided to prevent people creating unlimited numbers of "empty" accounts. If I had to guess, it would be an attempt to prevent people creating 15 empty accounts, putting their money into an address in account #15 and then wondering why they can't find their coins when they have to do a restore! |
|
|
|
I'm wondering what's involved and or if the old wallets are even accessible anymore. It was the original wallet version from the first year of bitcoins launch. Seed phrase and then the other password and so on.
Sounds like you're confusing several wallets into "one"... You talk about "wallet.dat" which is Bitcoin-QT/Bitcoin Core but then mention "Seed Phrase and then the other password" which sounds similar to the old blockchain.info recovery phrase and "second password". By "wallet file", perhaps you're thinking about the backup wallet file that you could download from blockchain.info? Note that "Passwords" (terminology used with Bitcoin-QT/Bitcoin Core is "passphrase") were only added to the wallet.dat in version 0.4.0 which was released 23 September 2011. Refer: https://bitcoin.org/en/release/v0.4.0 |
|
|
|
The ubuntu method might work but you should also send a mail to [suspicious email address redacted], a recovery firm that specializes in all types of cryptocurrency retrievals without payment of any upfronts.
I would not trust some "no history" newbie shilling a "recovery" site. That site looks very dodgy... I especially like the way they have a UK address and a North American phone number  Oh... and the premises at "94 Green Lane in Worcester"?  (note, the postcode listed on their website WR65 6YB doesn't actually exist)  |
|
|
|
It is likely that the OP simply has not "received" any funds to accounts that have already been added to Ledger Live. Ledger Live supports both Nested Segwit (P2SH-P2WPKH, aka "3-type") addresses AND Native SegWit (aka P2WPKH, aka "bc1") addresses... However, if one of your existing accounts has NEVER received any funds, then you won't be able to create a new account of that type... like in my wallet, I have the following accounts: "Bitcoin 1 (legacy)" - original account, that is well used "Bitcoin 1" - which is actually a 3-type SegWit account also used "Bitcoin 1 (Native SegWit)" - which has never been used So, because I have a "used" 3-type... and an "unused" native segwit... I can only create a "3-type" account:  If I add that account... and then try to add a new account, then because I now have both "SegWit" and "Native SegWit" accounts that are unused I am unable to add any new accounts at all.  If I were to now send some coins to "Bitcoin 2 (SegWit)"... Ledger Live would let me add a "Bitcoin 3 (SegWit)"... but still not let me add a "native segwit", because "Bitcoin 1 (native SegWit)" is unused. However, if I were to send some coins to "Bitcoin 1 (native segwit)" instead... Ledger Live would then let me add a "Bitcoin 2 (native segwit)", but would not let me add any more 3-type segwit accounts because "Bitcoin 2 (segwit)" is currently unused. If I were to send some coins to BOTH "Bitcoin 2 (segwit)" and "Bitcoin 1 (native segwit)"... then Ledger Live would let choose from BOTH "segwit" and "native segwit" account types when trying to add a new account type. In summary, Ledger Live will ONLY let you add the account type(s) where the last account of that type is already "used". |
|
|
|
Essentially, all you need is the private key for the BTC address that you sent BCH to. Do you have this or a way to get it? Ways to get the private key: - Export private key from "cash app" wallet - Do you have a 12/24 word seed mnemonic backup for "cash app" wallet? If so, private key can be derived from this I'm not familiar with what "cash app" is exactly, so I can't be more specific. Is it a custodial wallet or do you have access to private keys/backup mnemonics? Do you have a link so I can look further into it?If you're referring to this: https://cash.app/ Then, as nc50lc has noted... it's a custodial wallet, meaning that only they have access to the private keys. you will need to contact Cash.app support. |
|
|
|
You can simply shutdown dicebot and then delete the dicebot database file named "DiceBot.db"... or simply rename that file it if you think you want/need to access that history again at some point... The file will be in the directory you run the dicebot.  NOTE: If your Windows is setup to hide file extensions, it might just show up as "DiceBot"... but the file type will be listed as "Data Base File" like in the screenshot above. You can read how to show file extensions for Windows 10 here: https://www.tenforums.com/tutorials/62842-hide-show-file-name-extensions-windows-10-a.html |
|
|
|
Nice, I was suspecting it was about Roman numerals, glad you were able to solve this one, maybe you will join the games in a rank of magician? I strongly encourage you to do so, more competition
So, to get points and inventory items... I need to grab some of the "daily micro-giveaway" puzzles? |
|
|
|
It is pretty simple.
I don't like signing as proof I prefer coin in and coin out as proof of control.
I'm curious, what is your perceived difference between signing a message and moving coins to determine "proof of control"? Both require access to the private keys to be able to "sign" the message or transaction (or the ability to coerce someone who does into doing what you are asking). So I don't see how shifting funds is any more trustworthy than a signed message? |
|
|
|
Pretty much anything you do to Ledger Live itself is "harmless"... as you're really only affecting data on the PC... Like you could completely delete LL and all it's data and it's all pretty much recoverable from simply re-syncing once you've connected your device again. The "dangerous" stuff is the stuff that lets you do things to the device that might wipe it... like the "repair your device"... or "device setup"... but even then, that's only "dangerous" if you don't have your backup seed mnemonic |
|
|
|
i really need your idea guys. what will my bitcoin config file must looks like?
Firstly, your bitcoin config will not be causing the issues you are seeing. back to my node,in debuglog ive seen those old transactions the 400 and .36 btc was still there for relay. i then abandon the .36btc and then send it again to the same address but it says it cannot be broadcasted immediately. What was the exact error message? Can you screen shot it when you try and create/broadcast the transaction? i will try to apply zapwallettxes to config and maybe include mempoolexpiry to clear my wallet. then ill try to send my bitcoins again to my other wallet. Those items don't need to be applied in the config file to fix your issue. "zapwallettxes" is just a way to clear the local list of transactions in your wallet file... so that the blockchain can then be re-scanned and only related transactions that are currently on the blockchain or being broadcast/received from other nodes are then re-added. It is useful after you "abandon" a transaction to remove them from your transaction history list etc, if you don't want them to show any longer. Generally you only want to run this as a "one off", to clear the unwanted transactions... so, it probably shouldn't be in your config file, but used as a temporary command line argument when you start the node. "mempoolexpiry" is not going to solve your problem at all. It is not related to your inability to send the transaction. |
|
|
|
It appears that while things are working, I still get (in electrs) errors like " failed to send PeriodicUpdate to peer 81: sending on a full channel" and I can see that electrs keeps disconnecting my connections to it from different wallets. It appears that there must be some more arguments that could probably help my wallets not disconnecting the way they do in electrs.
It's like electrs can't keep up with the speed of things?
Possibly... I'm not sure what the scaling is like and how it handles a large number of wallets/concurrent connections. I use it basically as a replacement for EPS... so i generally only ever have 1 connection to it from one Electrum instance (with possibly multiple wallet files open). You'd need to contact the electrs dev (via github or the thread on here) and see if they can shed some light on it. |
|
|
|
Firstly, apologies for the delay in reporting the recent activity. I've been on a work trip and being away from home makes doing "proper" updates with pretty pictures and stuff difficult with my phone as I don't carry a laptop and my old Nexus 7 tablet is pretty much only useful for watching Netflix... and it struggles to do that! Anyway... there was some interesting movements with BTC recently, which saw some "interesting" trading action... and what I thought was the bot appearing to attempt to long and short at the same time... Anyway, it took a small profit one day, but the hangover from it (a filled order that didn't quite make the exit) ended up causing a minor loss the following day (and then 2 non-trading days):   So, it was quite a tidy win at 0.00349183 BTC which was around a ~5.67% gain... but then gave up -0.00033995 BTC (a minor 0.5% loss). So now, overall, the account balance is sitting at: 0.06472101 BTC, which is an overall loss of -0.03527899 BTC (-35.28%).
This is the order history for the recent activity:  This is the trade history for the recent activity:  Further updates as and when something happens and/or my schedule allows. |
|
|
|
Not sure that I quote from locked topics often enough for that to be useful for me, especially since you can do it manually in just a few seconds. I might give it a whirl if you upload your code though. Maybe we could move it to be beside the current "Quote" button rather than in the reporting toolbar.
I'm not terribly happy with the current location either tbh, it was simply "path of least resistance" I'm sure it'll be possible to move it wherever you want... it's just a matter of identifying the correct TD's or DIVs or whatever and inserting the button and input objects. 
A more pressing question, however: What are you using to change to that dark theme? I like the look of it. A browser extension called Stylus: https://add0n.com/stylus.html (It's a fork of "Stylish" I believe) and a modified version of "nex dark theme": https://userstyles.org/styles/173576/nex-dark-themeMy "current" version of the theme (made some alterations to fix a few little visual quirks): .tborder {
border: none;
background-color: transparent;
padding: 0
}
form#quickModForm > table.bordercolor > tbody > tr > td {
padding: 0;
}
/*استثناء عناصر من الغاء الحدود*/
#frmLogin table.tborder,
#creator table.tborder,
.tborder table#smfheader+table,
.tborder table#smfheader+table+table,
div#helpmenu+div#helpmain {
border: 1px solid #373b44 !important;
}
/**/
.tborder table#smfheader+table,
.tborder table#smfheader+table+table {
border-top: none !important;
}
.tborder table#smfheader+table {
border-bottom: none !important;
}
#upshrinkHeader2 { padding-bottom: 1px; }
/*--------استثناء عناصر من الغاء الحدود نهاية--------*/
/* خانات الادخال input */
input,
input[type="text"],
textarea,
select {
outline: none;
padding: 4px;
transition: all 0.2s;
border-radius: 3px;
}
input:disabled {
background-color: #25282f;
}
input[type="button"],
input[type="submit"] {
cursor: pointer;
padding: 2px 10px !important;
transition: all 0.2s;
color: #fff;
}
input:focus, textarea:focus {
border-color: #6393bf !important;
}
input, input[type="text"], textarea {
border: 1px solid #aaa;
}
select {padding: 2px}
/* الردود منفصلة كصناديق
-----------------------*/
#bodyarea > form > table > tbody > tr > td > table {
margin-top: 10px;
}
#bodyarea > form > table > tbody > tr:first-child > td > table {
margin-top: 0;
}
#bodyarea #quickModForm .bordercolor {
background-color: transparent;
}
#quickModForm .windowbg, #quickModForm #preview_body{
background-color: #f7f7f7;
}
#quickModForm .windowbg2 { background-color: #fff; }
#quickModForm .windowbg,
#quickModForm .windowbg2 {
padding: 0;
border-radius: 5px;
}
form#quickModForm > table:first-child > tbody > tr:first-child td.windowbg:first-child {
border-radius: 0 0 5px 5px;
}
#quickModForm td.windowbg > table > tbody > tr > td+td,
#quickModForm td.windowbg2 > table > tbody > tr > td+td{
padding-right: 25px !important;
padding-left: 25px !important;
}
#quickModForm td.windowbg > table > tbody > tr > td.poster_info,
#quickModForm td.windowbg2 > table > tbody > tr > td.poster_info {
padding-left: 10px;
width: 14%;
overflow: auto !important;
border-radius: 5px 0 0 5px;
}
#quickModForm td.windowbg > table > tbody > tr > td.poster_info {
background-color: #f3f3f3;
}
#quickModForm td.windowbg2 > table > tbody > tr > td.poster_info {
background-color: #f7f7f7;
}
/*-------- نهاية الردود منفصلة كصناديق --------*/
/*-------------------------
تعديلات بداخل المواضيع
--------------------------*/
.post { padding-top:5px; }
/* اخفاء Re:.. */
/* .subject a {display: none} */
/* تغير لون الفواصل */
hr, .hrcolor {
color: #d2d2d2;
background-color: #d2d2d2;
}
/* نهاية تعديلات بداخل المواضيع */
/*-----------------------------------
الاقتباسات
------------------------------------*/
.quote {
color: inherit;
}
.quote,
.quoteheader {
background-color: transparent;
border: none;
margin-top: 0;
}
.quoteheader {
margin-right: 3px;
}
.quoteheader:before {
content: url(https://i.ibb.co/W0hX5KP/qicon.png);
opacity: 0.1;
margin: 0 5px;
}
.quoteheader,
.quote {
border-left: 4px solid #ddd;
}
/*عند مرور الماوس*/
.quote:hover {
border-left: 4px solid #ccc;
}
.quoteheader:hover,
.quoteheader:hover + .quote,
.quoteheader:hover,
.quoteheader:hover + .quote
{
border-left: 4px solid #ccc;
}
/* الاقتباس اتجاة يمين
----------------------*/
div.post[dir='rtl'] .quoteheader,
div.post[dir='rtl'] .quote{
border-right: 4px solid #ddd;
border-left: 0 !important;
}
div.post[dir='rtl'] .quote:hover {
border-right-color: #ccc;
}
/* عند مرور الماوس اتجاة يمين*/
div.post[dir='rtl'] .quote:hover
{
border-right: 4px solid #ccc;
}
div.post[dir='rtl'] .quoteheader:hover,
div.post[dir='rtl'] .quoteheader:hover + .quote {
border-right: 4px solid #ccc;
}
/*---------- نهاية الاقتباسات ------------*/
/*-----------------------------------
تنسيق عنوان الموضوع
------------------------------------*/
#bodyarea table.tborder tr.catbg3,
#bodyarea table.tborder tr.catbg3 td {
background-image: none;
background-color: #5b7e9e;
}
tr.catbg3 #top_subject {
padding-top: 5px;
padding-bottom: 5px;
}
#bodyarea table.tborder tr.catbg3 td:first-child {
border-radius: 5px 0 0 0;
}
#bodyarea table.tborder tr.catbg3 td:last-child {
border-radius: 0 5px 0 0;
}
/*---------- نهاية تنسيق عنوان الموضوع ------------*/
#bodyarea > div.tborder > table.bordercolor {
border-radius: 5px 5px 0 0;
}
.catbg, .catbg2, .catbg3 {
border-bottom: 0;
}
.catbg, tr.catbg td, .catbg3, tr.catbg3 td,
.catbg2, tr.catbg2 td {
background-image: none;
background-color: #5b7e9e;
}
tr.catbg3 #top_subject {
padding-top: 5px;
padding-bottom: 5px;
}
table.bordercolor tr td.catbg3:first-child {
border-radius: 5px 0 0 0;
}
table.bordercolor tr td.catbg3:last-child {
border-radius: 0 5px 0 0;
}
.tborder > .catbg:first-child,
table.bordercolor tr td.catbg:first-child,
.catbg2:first-child {
border-radius: 5px 5px 0 0;
}
.bordercolor {
margin-top: 0 !important;
}
/* الهيدر */
.tborder #smfheader td.catbg:first-child {
border-radius: 5px 0 0 0
}
.tborder #smfheader td.catbg:last-child {
border-radius: 0 5px 0 0
}
/* اضافة لون للمواضيع المتحكمة من صاحب الموضوع */
#bodyarea tr.catbg3+tr td.smalltext {
background-color: #fffce5;
border-bottom: 1px solid #ffde7b;
}
/*---------- نهاية موضوع متحكم ------------*/
/*-----------------------------------
تغير الصور الشخصية لدائرية
-----------------------------------*/
#quickModForm td.windowbg > table > tbody > tr > td.poster_info img.avatar,
#quickModForm td.windowbg2 > table > tbody > tr > td.poster_info img.avatar,
table > tbody > tr > td.windowbg img.avatar,
form[name=pmFolder] img.avatar {
display: inline-block;
vertical-align: middle;
border-radius: 100px;
-webkit-border-radius: 100px;
-moz-border-radius: 100px;
-ms-border-radius: 100px;
-o-border-radius: 100px;
object-fit: cover;
border: 2px solid #fff;
-webkit-background-size: cover;
-moz-background-size: cover;
background-size: cover;
background: no-repeat center center;
box-shadow: 2px 2px 4px 0px #aaa;
}
/* الحجم بالمنشورات */
#quickModForm td.windowbg > table > tbody > tr > td.poster_info img.avatar,
#quickModForm td.windowbg2 > table > tbody > tr > td.poster_info img.avatar,
form[name=pmFolder] img.avatar /*بصفحة الرسائل*/ {
height: 4rem;
width: 4rem;
}
/* الحجم بصفحة العضوء */
table.bordercolor > tbody > tr > td.windowbg img.avatar {
height: 5.75rem;
width: 5.75rem;
}
/* الحجم بالهيدر العلوي */
#upshrinkHeader table > tbody > tr > td.windowbg img.avatar {
height: 3.5rem;
width: 3.5rem;
}
/* من الديف الحاويoverflow اخفاء */
#quickModForm td.windowbg > table > tbody > tr > td.poster_info div[style^="overflow"],
#quickModForm td.windowbg2 > table > tbody > tr > td.poster_info div[style^="overflow"]{
overflow: unset !important;
}
/*------ نهاية تغير الصور الشخصية لدائرية ------*/
/* اخفاء حدود القائمة العلوية */
.tborder table#smfheader+table,
.tborder table#smfheader+table+table {
border: none !important;
}
div[style="border:2px solid orange; background-color:lightyellow; padding:10px; margin-bottom:5px"] {
color: black
}
div[style="border:2px solid red; background-color:#FF9696; padding:10px; margin-bottom:5px"] {
color: black
}
div[style="border:2px solid red; background-color:#FF9696; padding:10px; margin-bottom:5px"] a {
color: #666666
}
/* خانات الادخال input */
input, textarea {
border-color: #424448 !important;
background-color: #191c23;
}
input:focus, textarea:focus {
border-color:#567ee0 !important;
}
input[type="button"],
input[type="submit"] {
border: none;
background-color: #3F51B5;
border-radius: 3px;
padding: 4px 7px !important;
}
input[type="button"]:hover,
input[type="submit"]:hover {
background-color: #5265d9;
}
/* الوان القوائم الفاتحة */
.titlebg, tr.titlebg th, tr.titlebg td, .titlebg2, tr.titlebg2 th, tr.titlebg2 td
{
border: none;
background-image: none;
background-color: #373b44;
}
/* لون النصوص بالثيم الاسود*/
body, td, th, tr,
.nav, .nav:link, .nav:visited,
a.nav:hover,
.windowbg, #preview_body,
.quoteheader, .codeheader, .code,
.windowbg2, .windowbg3,
.titlebg2 a:link, .titlebg2 a:visited,
.titlebg, .titlebg a:link, .titlebg a:visited,
.titlebg, tr.titlebg th, tr.titlebg td, .titlebg2, tr.titlebg2 th, tr.titlebg2 td,
input, textarea
{
color: #ccc
}
/* لون الخلفية بالثيم الاسود */
.windowbg, #preview_body {
background-color: #25282f;
}
/* الروابط */
a:visited {
color: #939dc5;
}
a:link {
color: #939dc5;
}
a.ul[href^="https://bitcointalk.org/"]:hover {
color: #89c775 !important
}
.edited {
border-bottom-color: #d6d6d6;
}
div#bodyarea .maintab_back a:link, div#bodyarea .maintab_back a:visited, div#bodyarea .mirrortab_back a:link, div#bodyarea .mirrortab_back a:visited {
color: #939dc5;
}
/* الوان خلفية الردود */
#quickModForm .windowbg, #quickModForm #preview_body,
#quickModForm .windowbg2 {
background-color: #23262f;
}
#quickModForm td.windowbg > table > tbody > tr > td.poster_info,
#quickModForm td.windowbg2 > table > tbody > tr > td.poster_info {
background-color: #20232b;
}
/* الفواصل */
hr, .hrcolor {
color: #393c44;
background-color: #393c44;
}
/* الوان الاقتباسات
--------------------------*/
.quoteheader, .quoteheader a {
color: #737c9e;
}
.quoteheader,
.quote{
border-left: 4px solid #3d444e;
}
.quote:hover
{
border-left: 4px solid #62676f;
}
.quoteheader:hover,
.quoteheader:hover + .quote
{
border-left: 4px solid #62676f;
}
/* الاقتباس اتجاة يمين
----------------------*/
div.post[dir='rtl'] .quoteheader,
div.post[dir='rtl'] .quote{
border-right: 4px solid #3d444e;
}
div.post[dir='rtl'] .quote:hover {
border-right-color: #62676f;
}
/* عند مرور الماوس اتجاة يمين*/
div.post[dir='rtl'] .quote:hover
{
border-right: 4px solid #62676f;
}
div.post[dir='rtl'] .quoteheader:hover,
div.post[dir='rtl'] .quoteheader:hover + .quote {
border-right: 4px solid #62676f;
}
/*---------- نهاية الوان الاقتباسات ------------*/
/* الصور الشخصية */
#quickModForm td.windowbg > table > tbody > tr > td.poster_info img.avatar,
#quickModForm td.windowbg2 > table > tbody > tr > td.poster_info img.avatar,
table > tbody > tr > td.windowbg img.avatar,
form[name=pmFolder] img.avatar
{
background-color: #fff;
border-color: #323640;
box-shadow: 2px 2px 4px 0px #121c27;
}
/* الوان عنوان الموضوع */
#bodyarea table.tborder tr.catbg3,
#bodyarea table.tborder tr.catbg3 td {
background-color: #373b44;
}
.catbg, tr.catbg td, .catbg3, tr.catbg3 td,
.catbg2, tr.catbg2 td {
background-color: #3f4554;
}
#bodyarea table.tborder tr.catbg3,
#bodyarea table.tborder tr.catbg3 td {
background-color: #373b44;
}
/* اضافة لون للمواضيع المتحكمة من صاحب الموضوع */
#bodyarea tr.catbg3+tr td.smalltext {
background-color: #292d38;
border-bottom-color: #373b44;
color: #fff
}
/* ----------------
تعديل الالوان
------------------*/
[style^="color: black"], [style^="color:black"] {
color: #d6d6d6 !important;
}
[style^="color: green"], [style^="color:green"] {
color: #5bb55b !important;
}
[style^="color: red"], [style^="color:red"] {
color: #ff3434 !important;
}
[style^="color: blue"], [style^="color:blue"] {
color: #1f81ff !important;
}
/**/
[style^="background-color: yellow"], [style^="background-color:yellow"] {
color: #000;
}
/* الوان شريط الانتقال بالاسفل */
.titlebg2 {
background-image: none;
border: none;
background-color: #2d313a;
color: #d6d6d6;
}
/* ايقونات الرد و التعديل و الحذف */
img.reply_button {
/* content: url(https://i.ibb.co/d6zXLq1/brown-quote.png); */
content: url(https://talkimg.com/images/2023/11/15/zcmMD.png);
}
img.modify_button {
/* content: url(https://i.ibb.co/dLtnpKp/brown-edit.png); */
content: url(https://talkimg.com/images/2023/11/15/zc6Jf.png);
}
img.remove_button {
/* content: url(https://i.ibb.co/vPDfyG9/brown-delete.png); */
content: url(https://talkimg.com/images/2023/11/15/zcPpZ.png);
}
/* ايقونة الاقتباس */
.quoteheader:before {
content: url(https://i.ibb.co/QpYLk0v/qiconw.png) !important;
opacity: 0.22;
}
/* لون الكود */
.code {
background-color: #2f323c;
border-color: #444850;
}
/*تحت التجربة*/
.windowbg2 {
background-color: #262931;
}
.bordercolor {
background-color: #363940;
}
body {
background-color: #191c23;
color: #fff
}
.windowbg3 {
background-color: #22242b;
}
/*---------------------------------
تغير خلفية القائمة العلوية مؤقتاً !!!
الافضل تخصيص الالوان اكثر حتى يكون اكثر تناسق هذا موقت
---------------------------------*/
/* delete this code If images are not displayed in the top menu*/
.maintab_back {
background-image: url('https://i.ibb.co/v1vrm0d/maintab-back.gif')
}
.maintab_first {
background-image: url('https://i.ibb.co/DKK4rrX/maintab-first.gif')
}
.maintab_last {
background-image: url('https://i.ibb.co/C9QxkDg/maintab-last.gif')
}
.maintab_active_first {
background-image: url('https://i.ibb.co/Q96FRdx/maintab-active-first.gif')
}
.maintab_active_back {
background-image: url('https://i.ibb.co/5Tk3s5j/maintab-active-back.gif')
}
.maintab_active_last {
background-image: url('https://i.ibb.co/drDZN4d/maintab-active-last.gif')
}
/* end top menu background image! code*/
/*------------------------------
شريط التمرير الجانبي
------------------------------*/
::-webkit-scrollbar {
width: 10px;
height: 8px;
}
::-webkit-scrollbar-track-piece {
background-color: #23262f; /*Global Track Peice(the slider noob.)*/
-webkit-border-radius: 6px;
}
::-webkit-scrollbar-thumb:vertical {
height: 50px;
background-color: #373b44; /* Up/Down slider background*/
-webkit-border-radius: 6px;
}
::-webkit-scrollbar-thumb:horizontal {
width: 50px;
background-color: #373b44; /* Side/Side slider background*/
-webkit-border-radius: 3px;
}
/* الشريط بالكود */
/* الحجم */
.code::-webkit-scrollbar {
width: 7px;
height: 7px;
}
/*مقبض التمرير*/
.code::-webkit-scrollbar-thumb:vertical {
height: 50px;
background-color: #13161c; /* Up/Down slider background*/
-webkit-border-radius: 6px;
}
/*خلفية شريط التمرير*/
.code::-webkit-scrollbar-track-piece {
background-color: #23262f; /*Global Track Peice(the slider noob.)*/
-webkit-border-radius: 6px;
}
/* نهاية الشريط بالكود */
.windowbg b a {
color: white
}
/* ------ نهاية شريط التمرير الجانبي ------- */
|
|
|
|
So you're saying that a user could "deposit" $10000 of USDT to StiB... earn 12% over 1 year and then earn $1200 in interest... and then they will be able to withdraw $11,200? And would also have $1190 worth of "credit" that they could then borrow with NO collateral required? Also, what KYC requirements is this service going to have? |
|
|
|
Ok... so someone posted something today regarding reporting posts from a user's post history, and someone linked back to this thread. Not sure why exactly, but that re-ignited my desire to see if there was a way to "automate" quoting of posts in locked topics... And I managed to add in a "hack" that more or less works. It isn't automated to the point of simply giving me a "quote" button on locked threads... but it is as simple as copying a URL and clicking a button. So, I now have a "quote" button and "locked quote URL" text box: 
If I copy the "permalink" URL for a post in a locked topic... say the URL for Post #3 from the locked thread here: https://bitcointalk.org/index.php?topic=5216639.msg53575600#msg53575600I can copy/paste that into the "locked quote URL" text box: 
Then I can click the "quote" button and it will automagically redirect to a slightly custom "post" URL which includes a the custom "lockedtopic" value in URL which the board ignores but is useful for passing info : 
et voilà, the script then automagically modifies the pre-populated "textArea.Value", so that the "link=topic=TOPIC_ID" value gets changed to "lockedtopic" value:  And you're free to copy/paste the correctly formatted quote, with correct topic link and timestamp as you please. Like this: That was a clever and imaginative way to troll though. Smart dude. Theymos should reward him first (merits maybe?), ban after.
KNOWN ISSUES/LIMITATIONS:1. I've configured it to wipe the "subject" value, to avoid accidentally posting into the new thread with the subject line of the locked thread that you're quoting from. Not sure how to fix this so that the subject is the same as the "unlocked" thread you're trying to post to? For now, the workaround is to simply copy/paste the "locked quote" from the newly opened "post" window to a different quickpost/reply box. 2. You can only do one quote at a time. I would guess that theoretically it should be possible to do a comma separated list of locked quote URLs and then have the script open multiple tabs at once, but that doesn't seem like much of a timer saver of doing them one at a time  3. Currently only works from "thread view" in an unlocked thread... It doesn't work from the "post history view"... as you need a guaranteed "unlocked topic" to send to the "post" action, otherwise you'll get the "This topic is locked, you are not allowed to post or modify messages..." error Possible workaround would be to create my own topic somewhere that I'm never going to lock and use that as a "default"? 4. The code is pretty hacky and could probably be tidied up and refactored If anyone is interested, let me know and I can look at posting up the modifications required. |
|
|
|
Perhaps you are attempting to go a bit too technical for "B&H"? Based on my experiences in that board, your suggested topics might be too low level for the audience. Maybe try focusing on high level topics first, that still require some thought and effort on behalf of the respondents. As an example of the things suitable for the target audience, maybe consider getting newbies to investigate things we see repeatedly asked by newbies: Why did my wallet address change? (address re-use/deterministic wallets) Why does my transaction spend 0.001 BTC when I only tried to send 0.0003 BTC? (spending whole UTXOs) Why does my transaction to send 0.0003 BTC also send 0.0007 to some unknown address? (change) This guy gave me an address with 0.1 BTC in it, how do I spend it? (watching wallets vs 'normal' wallets) Why do I have to download 280+gigs for Bitcoin Code? (blockchain fundamental, need to start at the beginning to verify) Basic stuff? sure... but, in my opinion, having a solid grasp of the basic fundamentals is required before you can start asking about orphan blocks and soft forks. They need to learn to walk before they can run! |
|
|
|
|
Show Posts
