Hello Can anyone say if luckygames.io is supported on Seuntjie dicebot.
All supported sites are listed right on the front page of bot.seuntjie.com: https://bot.seuntjie.com/
|
|
|
bob, well i mean if you want to update the firmware on nano ledger, you still need it connected to a computer right?
Well obviously. How are you going to magically transfer a firmware to the device if it isn't connected to your computer? Also i dont think i tried this but if you try pressing buttons on the nano ledger s without connecting it to anything, does something show up on the screen or not?
If it isn't connected to anything... then absolutely nothing will happen. The device needs external power... it doesn't have an internal battery. The only way to power it is via the USB cable. So, it needs to be connected (via USB cable) to an outlet providing the appropriate power. This doesn't necessarily need to be a PC... you can connect it to a phone/tablet using a USB-OTG cable... or you can even connect it to a phone charger and it will start up. I connected mine to a USB port on a Television once. Both the TV and the Ledger Nano S are still functioning Obviously, connecting it to a phone charger will power the device and you'll be able to unlock it, wipe it, set it up etc... but you cannot transfer any data to or from the device. bob and hcp, so everytime there is an update on ledger live... update it. Then connect your ledger nano s to it and check manager to see if there is firmware update, then always update it.
No... you should never update anything... ever... /s Of course you should update... I'm fairly sure I've told you this about 2347923179 times in various threads and PMs
|
|
|
Is that page meant to display a list of posts you have reported? All I see is my a brief overview of my "stats"... "You have reported 248 posts with 100% accuracy..." etc... but I don't see a list?
|
|
|
It doesn't change the actual title of the topic/thread... it only changes the "subject" of that particular post. So other users will still see the original topic title when they're browsing the board. Granted if someone then "quotes" the post with the *modified* title, they inherit that modified title... but is it really a big issue?
|
|
|
If anyone cares, I managed to get this working for Chrome... I had to use the Mozilla webextension-polyfill library to wrap the script as it uses the browser.* namespace... Chrome insists on chrome.* I also modified o_e_l_e_o's .css to fix the order of the buttons and also get the "Report as:" text into the correct place. As always... this is " AT YOUR OWN RISK"... I accept no responsibility if you get banned for spamming mods! 1. Download the latest browser-polyfill.js from here, put it in the same directory as the other files from OP: https://github.com/mozilla/webextension-polyfill/releases(HINT: click on the unpkg.com link... ie. for 0.4.0: https://unpkg.com/webextension-polyfill@0.4.0/dist/)2. Modify the manifest.json to reference the browser-polyfill.js BEFORE the other .js files and to fix the "version" error (apparently Chrome doesn't like the 'b' in 0.1b ): {
"manifest_version": 2, "name": "BCT Helper", "version": "0.1.1",
"description": "Adds some automation for bitcointalk.org.",
"content_scripts": [ { "matches": [ "*://bitcointalk.org/*" ], "js": [ "browser-polyfill.js","bct-content.js" ], "css": [ "bct-content.css" ], "run_at": "document_idle" } ],
"background": { "scripts": ["browser-polyfill.js","bct-background.js"] }, "permissions": [ "tabs" ] }
3. Enable "Developer Mode" in Chrome Extension settings 4. Then click "Load unpacked" in Chrome Extension settings, browse to the directory where you placed all the files and click "Select Folder" PROTIP: If you find that when you try to report a post, it opens a new tab in the background, but then doesn't appear to actually submit the report... try reading the OP again carefully NOTE: This fix is ONLY needed if you use o_e_l_e_o's .css!!!This is the fix for .css to put the "Report as:" text on the right with the buttons. div.post { border-left: 4px transparent solid; }
div.post.post-wait { opacity: 0.5; }
div.post.post-error { border-left: 4px red solid; }
div.post.post-success { border-left: 4px yellow solid; }
.bct-report-button-container { float: right; margin-top: 10px; margin-bottom: 40px; }
.bct-report-input { float: right; margin-right: 4px; height: 16px; }
.bct-report-button, .bct-report-button:hover { float: right; background-image: linear-gradient(#375F82, #88A6C0); border: 1px solid black; margin-left: 4px; padding: 3px 5px 3px 5px; transform: none; color: #ffffff; }
.bct-report-button:hover { cursor: pointer; }
NOTE: This fix is ONLY needed if you use o_e_l_e_o's .css!!!This is the fix for the "copy from:" and "move to:" buttons and text boxes being in the wrong order You need to replace the code in bct_content.js with the following: console.log("BCT-CONTENT initialized"); console.log("Page: " + window.location.href); console.log("Referrer: " + document.referrer);
function process_background_message(message, sender, send_response) { browser.runtime.onMessage.removeListener(process_background_message); console.log("Content script received background message: " + JSON.stringify(message)); if (message.action == "bct-tab-open-report" || message.action == "bct-tab-submit-report") { if (message.comment !== undefined) { document.getElementsByName("comment")[0].value = message.comment; } document.getElementsByName("comment")[0].focus(); message.result = "OK"; } if (message.action == "bct-tab-submit-report") { // mod report counts as post/PM for throttling - add a delay setTimeout(() => { send_response(message); // Uncomment the next line to allow reports to be submitted automatically //document.querySelector("input[type=submit][value=Submit]").click(); }, 5000); } else { send_response(message); } // this is needed to make the sender wait for a response return true; }
function report_post(post_container, thread_id, post_id, report_comment, auto_submit) { post_container.classList.add("post-wait");
let event_detail = { event_id: (Math.random().toString(36) + '000000000000000000').slice(2, 18), action_name: "bct-report", action_url: "https://bitcointalk.org/index.php?action=reporttm;topic=" + thread_id + ";msg=" + post_id, action_payload: { post_id: post_id, comment: report_comment, auto: auto_submit } };
browser.runtime.sendMessage(event_detail) .then((message_response) => { //console.log("message_response: " + JSON.stringify(message_response)); console.log("message_response size: " + JSON.stringify(message_response).length); post_container.classList.remove("post-wait", "post-error", "post-success"); post_container.classList.add("post-success"); }) .catch((error) => { console.log("Data request failed:"); console.log(error); post_container.classList.remove("post-wait", "post-error", "post-success"); post_container.classList.add("post-error"); }) ; }
function extract_ids_from_url(post_url) { let url_parts = post_url.split("#msg"); let post_id = url_parts[1]; let thread_id = url_parts[0].split(".msg")[0].split("?topic=")[1]; return [thread_id, post_id]; }
function create_button(post_container, button_title, report_comment, text_field, auto_submit) { let button = document.createElement("button"); button.className = "bct-report-button"; button.innerText = button_title; button.title = report_comment; button.addEventListener("click", (e) => { e.preventDefault(); if (text_field) { if (text_field.value.trim()) { report_comment += " " + text_field.value.trim(); } else { alert("Required value missing"); return; } } report_post(post_container, post_container.thread_id, post_container.post_id, report_comment, auto_submit); }); return button; }
function create_span(text) { let span = document.createElement("span"); span.innerText = text; return span; }
function create_text_field(hint) { let text_field = document.createElement("input"); text_field.className = "bct-report-input"; text_field.type = "text"; text_field.placeholder = hint; return text_field; }
// inject the buttons into each message document.querySelectorAll("div.post").forEach(post_container => { // Try to determine thread ID and post ID let link_object = null; if (post_container.parentNode.classList.contains("td_headerandpost")) { // Thread view // post -> td.td_headerandpost -> table ... -> div#subject_123456 link_object = post_container.parentNode.firstElementChild.querySelector("div[id^='subject_'] a"); } else { // Other views: patrol, user's post history, user's thread history let post_url_start = "https://bitcointalk.org/index.php?topic="; // post -> td -> tr -> tbody -> tr ... -> a[href contains #msg123456] link_object = post_container.parentNode.parentNode.parentNode.firstElementChild.querySelector("a[href^='" + post_url_start + "'][href*='#msg']"); } if (link_object) { [post_container.thread_id, post_container.post_id] = extract_ids_from_url(link_object.getAttribute("href")); if (post_container.thread_id && post_container.post_id) { let button_container = document.createElement("div"); button_container.className = "bct-report-button-container"; post_container.appendChild(button_container); button_container.appendChild(create_span("Report as: ")); button_container.appendChild(create_button(post_container, "zero value", "zero-value shitpost", null, true)); button_container.appendChild(create_button(post_container, "multi post", "two or more consecutive posts in 24h", null, true)); button_container.appendChild(create_button(post_container, "cross spam", "spamming their service across multiple threads - please check post history", null, true)); button_container.appendChild(create_button(post_container, "non-english", "non-English post on English board", null, true)); let url_field = create_text_field("URL of the original"); button_container.appendChild(url_field); button_container.appendChild(create_button(post_container, "copy from:", "copy-paste from:", url_field, true)); let board_field = create_text_field("correct board name"); button_container.appendChild(board_field); button_container.appendChild(create_button(post_container, "move to:", "wrong board, should be in", board_field, true)); } else { console.log("Found div.post and post URL but couldn't determine thread/post ID."); } } else { console.log("Found div.post but couldn't find post URL."); } });
if (window.location.href.startsWith("https://bitcointalk.org/index.php?action=reporttm")) { document.getElementsByName("comment")[0].style.width = "80%"; browser.runtime.onMessage.addListener(process_background_message); } if (window.location.href.startsWith("https://bitcointalk.org/index.php?board=")) { if (document.referrer && document.referrer.startsWith("https://bitcointalk.org/index.php?action=reporttm") && document.referrer.endsWith(";a") // after automatic submission ) { console.log("Attempting to close this tab..."); browser.runtime.sendMessage({ action_name: "close-this-tab" }); } }
|
|
|
Mods/Admins - Please kindly provide me with a list of your log (with IP used). I want to clear my account from this problem!
Sent PM to theymos and ask about your IP logs. No need... Theymos has added a function to be able to see your last 30 days worth of IP logs! Simply goto the following URL: https://bitcointalk.org/myips.php
|
|
|
I've read a little about SegWit, so you're saying it's still kinda new and those addresses (Bech32 & bc1) may not be supported at certain cites, Legacy is the standard, but might result in higher transaction fees? Which one would you recommend?
Personally, I'm using a "nested" SegWit (another type of "3" address) wallet... it's backwards compatible, so no issues with services saying "invalid address" etc and has most of the same SegWit benefits as "bc1"... but that doesn't help with the "signing" a message thing. Luckily, I have an "old" wallet with Legacy addresses available... and I staked one of those. You realise there is no reason that you can't simply use a new legacy or bc1 address for anything other than simply signing a message to stake the address right? You don't HAVE to actually use it to send/receive coins... You just need to make sure that you retain the appropriate private keys (backup wallet file or seed mnemonic etc) so you can re-sign later to prove "ownership" etc. [see below] I've planned on using "Replace By Fee" RBF option, so as to not have transactions get stuck or unconfirmed. I've also seen now that Electrum has a "mempool" option. Would it be better to use one or both of these in conjunction with SegWit or Legacy?
My advice, is always use RBF regardless of the address type... Legacy, Nested or Native SegWit... it'll save you one day when you get caught out by a massive spike in fee rates and you need to get your transaction pushed through. TBH, I don't pay much attention to the mempool/ETA thing in Electrum... as, I set fees manually after checking what is happening with fees on: https://jochen-hoenicke.de/queue/#0,24hand https://btc.com/stats/unconfirmed-txSo when I create a new Electrum wallet, will I be able to transfer my bitcoin from the old one to the new one and then delete the old one, without issues? Sorry for all the noob questions, just trying to figure this thing out. I'm just kinda concerned if I download a new Electrum wallet, will it conflict or replace the old one? Electrum allows you to have multiple different wallet files... you can even have them all open at the same time... so you don't need to re-download or replace anything... And I certainly wouldn't delete anything. Simply use the following menu option: "File -> New\Restore" You'll be able to create another wallet (different name)... and you can do this as many times as you like. You just want to make sure you give each wallet a meaningful name, so you know which wallet is which... and be very careful that when copying a "receive" address, that you copy it from the correct wallet!
Ok... so having said all that, in your instance, I'd simply create a new "Legacy" wallet called something like "StakedAddress"... take the first "receive" address from this wallet, stake it and sign a message with it over in the "staked address" thread. Then never use that wallet for anything but signing messages as required from your staked address... and you can continue to use your current wallet, until you decide which way you want to go (Legacy or SegWit etc).
|
|
|
But the actual link he posted (app.link/NNNNN) is unique, at least I couldn't find it on Google, so it looks like a referral. He could have just posted celsiusnetwork.app.link or celsius.network. Granted I don't know well enough how these branch.io referrals work so I'm not rushing to report it to mods. Just looks weird that this is his first post after a year-long break.
Most probably yes! I didn't check the quoted link and it actually looks like referral since appending a random digit to that link just redirects to the actual original web page.
It's definitely reflink "spam"... For the record, I reported it.
|
|
|
Basically, you would need to create a completely new wallet... with a completely new seed. "File -> New\Restore -> Standard Wallet -> Create a new seed" You can choose "SegWit" or "Legacy" during setup: Be aware that using Native SegWit (aka Bech32 aka "bc1") addresses *may* cause issues (as noted on the dialog) with some services and wallets (block explorers, exchanges, gambling sites etc) that do NOT as yet support "bc1" addresses Using "Legacy" addresses means you won't have any compatibility issues, but can result in slightly "larger" transactions that may mean you pay more in transaction fees.
|
|
|
Some exchanges do not recognize this address when withdrawing bitcoin.
Correct. There are a number of exchanges and other services that do not support "bech32" aka "Native SegWit" addresses. For now, your options are: 1. Continue to use "bc1"/bech32/Native SegWit addresses in Electrum and use blockexplorers/exchanges that support these addresses 2. Switch back to "Legacy" bitcoin addresses (need to specify during wallet setup): There is also a 3rd option, which is the backwards compatible "Nested SegWit" addresses which start with a "3". However, to create these addresses in Electrum (without a hardware wallet), you need to import a "BIP39" seed. However, there are quite a few issues with doing this and this setup is NOT recommended unless you fully understand the implications of doing so.
|
|
|
To expand on mocacinno's explanation...
Because you sent from your wallet to an address in same wallet, instead of showing your transaction as two different transactions: 1. "TransactionOUT = (-1 BTC - fee)" 2. "TransactionIN = (+1 BTC)"
Electrum "sees" it as just a single transaction: "TransactionOUTandIN = (-1 BTC -fee + 1BTC)"
Then it adds/subtracts all the values to get a single total value... so (-1 -fee + 1) => -fee: "TransactionOUTandIN = -fee"
That is why you see it on the Transaction History as showing just "-fee"... the out and in amounts cancel each other out. However, if you were to send to an address that is NOT in the same wallet, you would see the total "sent" amount, not just the fee.
|
|
|
"Cannot sign messages with this type of address: p2sh Signing with an address actually means signing with the corresponding private key, and verifying with the corresponding public key. The address you have entered does not have a unique public key, so these operations cannot be performed. The operation is undefined. Not just in Electrum, but in general."
P2SH = Pay to Script Hash... These addresses will start with a "3". As per the error message, P2SH addresses aren't necessarily created based on a single "private/public key"... Because of this, you cannot sign a message using these addresses as there is not public/private key to be able to sign the message with. Given that you're using Electrum, I would guess that you're either using a MultiSig wallet or, more likely, a "2FA" wallet (which is a special type of multisig)... these are actually created by combining multiple keys together to create the P2SH scripts. You need to use "Legacy" ("1"-type addresses) or Native Segwit (aka bech32 aka "bc1"-type addresses) to be able to sign messages.
|
|
|
As far as I'm aware, this issue has only occurred once... and only for devices on the 1.2 firmware and it was only caused because of the switchover from Chrome Web Apps to Ledger Live. It's not like it happened overnight and suddenly you couldn't update your device. I mean, the 1.3 firmware was released around Feb/Mar 2017!!?! That is over two years ago... and well before Ledger Live was released. In any case, I don't anticipate there being similar problems going forward (assuming you're on at least 1.3.1 or higher and can use your device with Ledger Live) It's no different to any wallet (aside from paper wallets) really... look at things like MultiBit, MultiBit HD... They quietly "died" and the wallets effectively became unusable. Developers usually do their best to go for backwards compatibility, but sometimes the situation will dictate that an update "breaks" something. Ledger were kind of "forced" into the Ledger Live situation due to Google dropping Chrome Webapp support. Would ledger try to fix this issue?
They have... they're giving replacement devices. In any case, as long as you have your seed mnemonic safely and securely backed up... you should still be able to recover your funds.
|
|
|
The coinmixer.** is a fake clone of coinmixer.se ( archive) that shut down a year ago. The current domain actually redirects to their announcement about shutting down. LOL... this is why you shouldn't "forum" late at night... misread coinmixer as chipmixer...
|
|
|
You need to connect the device... then select "Manager" in Ledger Live... then click on the device to allow ledger manager. It will show you the current version installed: If there is a new firmware, it will tell you on that Manager screen and have an "update" button available: image borrowed from bitgearOther ways to know if new firmware is available? Follow Ledger on Twitter or check their blog regularly
|
|
|
It's definitely sock puppets... bumping threads that start with the referral link... I mean, look at this: Here the user states they've been a user for a month... ... I;ve been using this platform for about a month now and it's great. ...
Then just over a month later... "I just signed up today" ... I've only signed up today and i'm very happy with the platform for numerous reasons :- ...
It's just a bunch of sock puppets shilling for Publish0x... while bumping reflink spam
but maybe we were wrong and every article shared to have that code? so any expert on bounty0x platform?
Just read their instructions for "Ambassadors" (aka reflink spammers)
|
|
|
I am sure I have not made any messages with plagiarism! And not spam on the forum!
Do you want to rethink that statement? Your post is the exact definition of plagiarism... Are you seriously? A post that was published almost two years ago? This was my second post on the forum, I was a Newbie. Is this really a serious reason for blocking?
Yes. Perhaps you should have read the rules before posting. Also, given your post history is almost entirely just bounty hunting posts... I don't anticipate the mods will consider granting any sort of temp+sig ban leniency.
|
|
|
That's a very old version of Ledger Live, we're currently at version 1.9.1... and my understanding is that firmware 1.2 never connected to ANY version of the Ledger Live. You needed to be on firmware 1.3.1... and the only way to get from firmware 1.2 to 1.3.1+ was by using the old Chrome Ledger Manager plugin. I'm led to believe that the Chrome Ledger plugin no longer works for firmware updates. I'd rather find a way to update it - if anybody can help, I would appreciate it so much.
Did you try my suggestion in your other thread? I think the stumbling block will be finding a copy of the firmware to be able to flash it... it's possible you need to update the bootloader as well, hence the requirement to actually replace the device. Honestly, I think the best solution is to contact Ledger support, advise you are on firmware 1.2 and ask them directly what you need to do to fix this issue. As mentioned in my other post, the Ledger devs/support seem a lot more active on reddit that here: https://www.reddit.com/r/ledgerwallet/
|
|
|
This is very confusing, why did the brainwallet suggested the other address and verified the message with it? I have to read more how this is possible, often happens that man has to edit the signed message to get it verified. The associated public key can be derived from the signature... brainwalletx is just encoding it as a legacy address as it doesn't allow "signing" with bech32 like Electrum does.
|
|
|
Paid 0.2 bitcoins to https ://coinmixer.es/ (SCAM! - DO NOT USE!), you will receive a shit. If you try to email them, no one answers.
How did you find that URL? Was it from a Google search? EDIT: Ignore the ramblings of a tired man with not enough coffee! obviously, coinmixer =/= chipmixer For reference, the ONLY two legitimate URLs for coinmixer chipmixer are: clearnet: https://chipmixer.com/and TOR: http://chipmixerwzxtzbw.onion/They are both in every chipmixer signature on this forum
|
|
|
|