When trying to click on edit, the page flips to the top and thats all that happens. I tested firefox and chromium browser (Linux). Both the same result.
Don't know why still can't edit my last post :(.
And the privie doesn't show anything
What to do ? (most explanation from mac tutorial but its working with linux too)
Downloading core Wallet zip from the Burst App Team
Actually the newest stable Version is BRS 2.5.3
Type: sha256sum burstcoin-2.5.5.zip in the terminal (from the download folder) to run sha256 check for security reasons and check if the sha256 is the same like on your output
Zip SHA-256: ee8bde45e3c10750ef62572cf347bcfde499950b7528eced3677177e47c779ae
Please make sure you are running Java 8 or higher
Creating an database. The program for this database you are using is maria:
2.1 Search for maria in the software repository and install maria
2.2 go to the terminal and type "sudo su" and press enter then you are on with root rights
Type the following, one line at a time, pressing enter step by step.
2.3 mysql -u root -p -h localhost
(The default password for MariaDB is blank. If it asks you for a password, simple press enter)
2.4 CREATE USER 'burstwallet'@'localhost' IDENTIFIED BY 'password';
(Replace password by your own password)
2.5 GRANT ALL PRIVILEGES ON burstwallet.* TO 'burstwallet'@'localhost';
2.6 CREATE DATABASE burstwallet;
2.7 Press ctr + c to exit
Got to your download folder and unzip burstcoin-2.5.3.zip
3.1 go to the burstcoin-2.5.3 folder and then open the conf folder
3.2 open brs-default.properties
3.3. search for:
Database connection JDBC url
Append ;AUTO_SERVER=TRUE to enable automatic mixed mode access.
DB.Username= here type burstwallet, burstwallet is your username
DB.Password= here type your password you set in 2.4
Don't forget to activate BRS for using maria db in the brs-default.properties. You have to delete # in front of the lines mentioned in 3.3. (and you have to set # in front of the lines for H2, after fresh install maria db is not activated).
It should look like this in your config:
DB.Password= typer here your password set in 2.4
save your changes.
Start BRS 2.5.3 Wallet
4.1 go to the burstcoin-2.5.3 folder (and open the terminal)
4.3 type: ./burst.sh
4.4. The Wallet is starting with maria.db database
(blockchain is saved in /var/lib/mysql/burstwallet, the burstwallet is the database you created in 2.)
4.5 type 127.0.0.1:8125 in your browser and start the wallet interface
Conclusion: You create a maria database called burstwallet and you created a maria user called burstwallet and set a password for your database. Then you set your username and password in the brs-defaults.properties file in the conf folder from your burstcoin-2.5.3 folder and then your started your wallet.
And the BRS 2.4.0 shows only Peers with 2.4.0 as up to date. BRS 2.3.0 are shown as not up to date. In my case only 6/25 are up to date (the 6 are running 2.4.0 and the rest 2.3.0).
Therefore Downloading blockchain from scratch is realy slow at this time.
And the Java is running all CPU Cores (4 of 4) on 100 % during running the wallet BRS 2.4.0.
Actually for me the 2.4.0 is not a good choice. The 2.3.0 is running smooth.
@ryanw Harry says the solution for the warning message.
Using Java 8 and all warning messages during startup are gone but when testing 127.0.0.1:8125 the same message:
"Warning!This node is not running on your local computer. Be cautious when using public wallets" is shown.
So i know i am running my node on my local computer but the BRS 2.4.0 Wallet is showing me another information although using Java 8.
I can't understand "This node is not running on your local computer" why BRS 2.4.0 is showing this message ?
@haitch Hi i am just testing the new wallet and got some issues. I posted my issue on:
Some advice ?
Hi i am just trying the BRS 2.4.0 and got this warning on every start.
[INFO] 2019-07-02 18:30:20 brs.db.sql.Db - Using SQL Backend with Dialect MariaDB
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.jooq.tools.reflect.Reflect (file:/home/.../burstcoin-2.4.0/burst.jar) to constructor java.lang.invoke.MethodHandles$Lookup(java.lang.Class)
WARNING: Please consider reporting this to the maintainers of org.jooq.tools.reflect.Reflect
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
And when testing 127.0.0.1:8125 I got this message:
Warning!This node is not running on your local computer. Be cautious when using public wallets.
Don't know what is going on but it's not normal that way.
Some advice ?
Whats is the community.
There can be no real community in forums.
If i would create a new coin for PoCC like Chia or BHD and i dislike the other coin like Burst.
I would go to the forums create an account and shout at the developer team until they stop development. Nice and easy if that is working.
Perhaps we should have a look on SmartCash. What if we get an similar voting system which depends on holding coins. So if we can ask the community for decicions. And only the real invested can vote. So we know that every man who is voting is realy invested and the more the more oting is possible.
The end is always the beginning of a new. We have to think of possibility to solve problems in burstcoin in a less toxic and not destroying way.
They should have informed the miners before testing. That was the failing communication. I think they don't come back. They don't want to come back. And in the end of my text i wrote it. They seems to be highly skilled developers and it's hard to believe that they didn't know what shitstorm from the community comes on dual mining and not informing about that before.
It seems they looked for a way out and used the community shitstorms to exit burstcoin development.
So if the community doesn't matter like they say they would have working on Dymaxion without drama . It 's like in the real world on the working place. If yout want to quit your job you find a reason to quit without saying the real reason if you don't want to.
Perhaps we get a fork or something else from the POCC, we will see.
POCC is now leaving BURST, they wrote it on Twitter:
I kbow its far in the future. Perhaps end 2019 or 2020 but when i think of PoC3 I am asking me some questiongs.
Why should a miner store PoC3 data. That would take all his traffic from his internet connection and the speed goes down ?
Why should someone store his content in PoC3 ?
@tedrogers Hi i am using CreepMiner for several months. Intensity is setting the core CreepMiner will be using for mining. So in general Intensity you have to the threads (for example: 8 Ccore + Hyperthreading = 16 Threads = Intensity setting to 16)
The more threads the faster is the reading.
The Intensity is setting the threads. Why your core i7 is creating an error with values grater than 8 isn't clear.
In my case the threadsetting with the Intensity works fine and Creep is running good.
actually i am looking on Xchange.me homepage for some information. I checked the trades between Poloniex, Bittrex and Xchange.me and i can say that Xchange.me has a good exchange rate in comparison to Poloniex and Bittrex.
So all in all it seems for me easier and a bit more free and anonymous trading of Burst on Xchange.me. Until now it didn't trade on Xchange.me but i am thinking to go there instead of Bittrex and Poloniex . Xchange.me seems not be in the us. It seems to be in Poland but it don't of this is a good thing or not.
Has someone else tried Xchange.me ? Some experiences ? Is it serious ?
i found the new Wallet on github but in the forum (reddit, burstforum, GetBurst) there was no message about the new software or i didn't find it.
So if someone else has a account on reddit or GetBurst write a short message for the people.
I checked the network status and at a first look there are almost zero user of the new wallet.
Did i miss something ? All the miner and user doesn't take a look on the new wallet ?
i found some strange behavior on Wallet 2.2.2. Every 2-3 day it suddenly stucks. For some reason exactly at that time i can see a block wining. First time i thought it was my fault and that i didn't see a block wining but after three times of that happening i am sure that my CreepMiner (1.8.3) shows a block winning which doesn't exist.
On my deadline overview i can't find any block that should have been wining something. But i am thinking this one:
When wining a block the wallet chrashes or get stuck so i can't see the wining block deadline.
Then I restart the BRS 2.2.2 Wallet and it goes on like normal. But in some days this "winning Block stuck" comes again.
Technically i should win some blocks during some but the last 7 days i didn't won anything.
So i can't find the issue but i think there is one issue.
What are your experiences any hints ? Could there be some forks out there and i am permanently on the wrong fork ?
What I don't like are the dominance of the PoCC Pools, i think this isn't good for burstcoin. Why are no more solo miners or some other big pools ? Could this be a part of my problem ?
Thanks for all answers,
so i replottet everythig with evanger Plotter and now using creep Miner 1.8.3.
Everything runs fine now. I am thinking that the converting tools made some errors.
my BRS Wallet 2.2.2 is at 526002 and the PoCC are on 526012 at the same time.
The Explorer cryptoguru shows the Block 526001 as the last block at 2018-08-22 18:20:31.
So i am thinking my wallet is on the correct Block with 526002 but the PoCC Pools run on block 526012.
So who is correct ? Some forks out there ?
i am on solo mining and i have updated to the newest Wallet BRS 2.2.1.
I got this error on solominig with CreepMiner 1.8.2
On first tests with the newest PoC2 converter engraver the new PoC2 file was working without error message. It was only a small plotfile so now i am creating bigger ones and testing again.
In think i have a couple for issues: bad PoC2 files, RAM and forwarding issue on CreepMiner
During using the forwarding feature of CreepMiner it seems that the RAM and swapfile is fully filled then the Miner crashes.
I am hoping with the new plotter (engraver) the different deadline error is gone and i am hoping that CreepMiner can handle the RAM during forwarding in the future without crashing.
When everyhing runs fine i write an how to for all other Linux users
Thank you for your help. I just spend 10 days of PoC2 creating but i will test the new Plotter and tell the results in this Post for all the other people in this forum.
I am just testing my new POC 2 files with CreepMiner. On Linux.
Everytime I got this issue with my PoC2 file: "The pool calculated a different deadline for your nonce than your miner has!"
It's a bit confusing cause PoC1 files are working fine without any issue on CreepMiner.
I wrote on github to the developer of CreepMiner (https://github.com/Creepsky/creepMiner/issues/417) but perhaps someone here has a solution or the same issue.
I created the PoC2 files with "cg_obup-PoC2" Plotter (the only Plotter for Linux)
Turbo Plotter can be used for Linux to, but i need more possibilities so set the amount of nonces that has to be plottet and in the linux version of turb plotter i can only set the startnonce and the RAM and nothing else.
Perhaps cg_obup-PoC2 Plotter is creating bad POC2 files ?
Just have a look on my github link, there is everything explained, i don't want to type everything again :).
Are there some Linux guys out there who can tell me how they created PoC2 files (which program) and how its working for them ?