Bitcoin Forum
May 05, 2024, 11:32:28 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [READ BEFORE POSTING] Tech Support Help Request Format  (Read 54964 times)
achow101 (OP)
Moderator
Legendary
*
Offline Offline

Activity: 3388
Merit: 6581


Just writing some code


View Profile WWW
January 06, 2017, 05:06:46 PM
Merited by Welsh (5), LoyceV (4), ABCbits (1), digaran (1), irhact (1)
 #1

This is a continuation of https://bitcointalk.org/index.php?topic=1282666.0 to actually make the format standard and stickied.



The Format


When creating a new help request in the Tech Support section, please use the following format. It will make it easier for others to help you as this format contains the information that is needed to provide the proper help.

Quote from: Standard Format
Bitcoin Client Software and Version Number:
Operating System:
System Hardware Specs:
Description of Problem:
Any Related Addresses:
Any Related Transaction IDs:
Screenshot of the problem:
Log Files from the Bitcoin Client:



Explanation of each field

Bitcoin Client Software and Version Number: The name of the software you are using and the Version number. We will always need to know this information.

Operating System: The name, version number, and bitness of your operating system. This is not always necessary. It is only needed for issues with your Bitcoin Client.

System Hardware Specs: The CPU, RAM, and Hard drive space of the computer that you are using. This is not always necessary. It is only needed for issues with your Bitcoin Client.

Description of Problem: The description of the problem you are having. This is always necessary. We need to know what is wrong.

Any Related Addresses: Any addresses related to the problem you are having. This is not always necessary. We only need to know this if you are having issues with transactions.

Any Related Transaction IDs: Any transaction IDs related to the problem that you are having. This is not always necessary. We only need to know this if you are having issues with transactions.

Screenshot of the problem: A screenshot of the problem that you are having uploaded to an image hosting service such as https://imgur.com. This is not always necessary. It is only needed for issues with your Bitcoin Client.

Log Files from the Bitcoin Client: A link to the log files created by your client uploaded to paste sites such as https://pastebin.com. This is not always necessary. It is only needed for issues with your Bitcoin Client. Not all software have options for exporting log files. If the log file is too large, just paste as much as you can from the bottom of the file.



Examples

The following are two example reports. The first example is one for a software client issue. The second example is for a transaction issue.

Quote from: Example 1
Bitcoin Client Software and Version Number: Bitcoin Core 0.13.1
Operating System: Windows 10 64-bit
System Hardware Specs: 4.0 GHz Quad Core CPU with 8 GB RAM and 50 GB free hard drive space.
Description of Problem: Bitcoin Core seems to be stuck while synching.
Any Related Addresses: None
Any Related Transaction IDs: None
Screenshot of the problem: https://imgur.com/a/zMnKk
Log Files from the Bitcoin Client: http://pastebin.com/tfqN34DW

Quote from: Example 2
Bitcoin Client Software and Version Number: Electrum 2.6.4
Operating System: Ubuntu 16.10 64-bit
System Hardware Specs: N/A
Description of Problem: I received a transaction several hours ago and it still has not confirmed
Any Related Addresses: 16mT7jrpkjnJBD7a3TM2awyxHub58H6r6Z
Any Related Transaction IDs: 4b54637c43beba0eae0cb0a8e139da3e170a941978d47aa5a37b17ff854939c1
Screenshot of the problem: N/A
Log Files from the Bitcoin Client: N/A



If you have any issues with getting any of these fields, still make your help request post and state that you have issues with getting the information for the fields that you have issues with. Users here will guide you on how to get it.



This format can change and evolve as it is used and other users comment on it.

1714951948
Hero Member
*
Offline Offline

Posts: 1714951948

View Profile Personal Message (Offline)

Ignore
1714951948
Reply with quote  #2

1714951948
Report to moderator
1714951948
Hero Member
*
Offline Offline

Posts: 1714951948

View Profile Personal Message (Offline)

Ignore
1714951948
Reply with quote  #2

1714951948
Report to moderator
1714951948
Hero Member
*
Offline Offline

Posts: 1714951948

View Profile Personal Message (Offline)

Ignore
1714951948
Reply with quote  #2

1714951948
Report to moderator
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714951948
Hero Member
*
Offline Offline

Posts: 1714951948

View Profile Personal Message (Offline)

Ignore
1714951948
Reply with quote  #2

1714951948
Report to moderator
1714951948
Hero Member
*
Offline Offline

Posts: 1714951948

View Profile Personal Message (Offline)

Ignore
1714951948
Reply with quote  #2

1714951948
Report to moderator
shorena
Copper Member
Legendary
*
Offline Offline

Activity: 1498
Merit: 1499


No I dont escrow anymore.


View Profile WWW
January 06, 2017, 06:17:45 PM
 #2

I personally think "steps you took before the problem occured" help out a lot in understanding the issue and giving good advice. It also helps if the title is a short summary of the problem (yeah I know, Id add it anyway), whether or not the person asked elsewhere for advice (e.g. xpost with stack exchangen) to avoid redudancy and what steps they already did in an attempt to solve the problem.

Edit: also maybe a few "donts", e.g. dont add nonsense votes or make the thread self moderated for no reason.

Im not really here, its just your imagination.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!