So now falling back to our humble beginnings... sigh.... Wait thats great! Scanning my inbox for the last part of the deal with coinexchange.io.
"L." from coinexchange sent me a freshdesk ticket # 17166:
Hi Biblepay,
Yes, we can guarantee listing, if we from degree didn't we would of course refund it.
Sincerely,
CoinExchange.io Support Team
Ticket: https://coinexchangeio.freshdesk.com/helpdesk/tickets/17166
He sent this 50 days ago and asked for 2 BTC to be listed on coinexchange. Of course with the other funds tied up, I didnt jump on it.
So thats where we are on this one. I sent him an email asking if the deal is still good.
We would need a fundraiser for this if we did it. Ill ask him if he will take payments.
Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 678. (Read 243376 times)
January 25, 2018, 11:50:24 AM
January 25, 2018, 11:44:58 AM
Sure post tBBP address there and I will send you some.
Ok I will post tBBP addresses once I have my system set up. Making the network cables now first time doing it so I have to learn first lol.
January 25, 2018, 11:29:14 AM
Btw, update on 1.0.8.7:
1.0.8.6 is still all you need to pool mine properly (it includes the extended solution packet) and its also all you need to avoid crashes - for the sanctuaries (it includes the line of code that allows a Sanc to handle a missing vote. If you are wondering How that is even possible, its because Dash fixed the issue in Evolution while we fixed it in a version that was pre-evolution, and its slightly different code, but it works now). Anyway my point is 1.0.8.6 fixes the sanctuary crash and allows you to pool mine after block 27500.
1.0.8.7 only adds one debug field to getmininginfo. This field allowed me to install biblepay on some reference machines, and simulate a new block with a static timestamp and a 0 nonce - to see if the base block hash could be made unique. It worked, as long as you have more than 1 bbp in the wallet, the packet is unique. (Another words, a botnet with 0 in the wallet will have a propensity to mine less efficiently if they all create the same base blockhashes). The test succeeded, and I believe anyone mining on 1.0.8.6 with more than 1 bbp will be mining distinct packets (IE helping us drive up the difficulty and solve pool shares).
1.0.8.6 is still all you need to pool mine properly (it includes the extended solution packet) and its also all you need to avoid crashes - for the sanctuaries (it includes the line of code that allows a Sanc to handle a missing vote. If you are wondering How that is even possible, its because Dash fixed the issue in Evolution while we fixed it in a version that was pre-evolution, and its slightly different code, but it works now). Anyway my point is 1.0.8.6 fixes the sanctuary crash and allows you to pool mine after block 27500.
1.0.8.7 only adds one debug field to getmininginfo. This field allowed me to install biblepay on some reference machines, and simulate a new block with a static timestamp and a 0 nonce - to see if the base block hash could be made unique. It worked, as long as you have more than 1 bbp in the wallet, the packet is unique. (Another words, a botnet with 0 in the wallet will have a propensity to mine less efficiently if they all create the same base blockhashes). The test succeeded, and I believe anyone mining on 1.0.8.6 with more than 1 bbp will be mining distinct packets (IE helping us drive up the difficulty and solve pool shares).
So I should add at least 1 BBP to all my miners?
I can also add some miners to testnet if still needed? but I won't have any tBBP can someone help with that?
I recommend adding 10-100 bbp in random amounts to active miners as you upgrade to 1086+.
Its not going to be a magic hash increase, but what that will do is ensure your base block hash is unique globally, and what that will do is as that unique miner increments its nonces and timestamps, it is not going to interfere with any other miner systemwide. And as a community that is important, because that will solve more pool blocks and cause the diff to rise (which helps squeeze out the botnet who may be mining with 0 bbp).
Sure post tBBP address there and I will send you some.
January 25, 2018, 11:25:57 AM
Alright, the new core wallet is almost ready, but don't feel overly rushed as this version requires a mandatory upgrade for pool miners only before block 27500. If you have a lot of pool miners to upgrade you can start pulling down the linux version (1084) now, but I will announce the release soon (when windows is ready).
So now that the upgrade is almost ready, Ill go into a little more detail as to why the 5 accounts were banned.
I have reason to believe one Hong Kong mining operation has been falsifying partial pool solution packets that hit as share solutions. Basically they are running the PCs in parallel and finding the distinct biblehash, and then leaving the thread in solo mining mode for a certain percentage of the time so as to trick the pool only when it asks how the thread is doing.
So this caused me to write a report on any miner who has not been solving actual blocks (IE MinerWhoFoundBlock) and therefore I banned all miners who have more than 10 machines pointed at the pool who have not found a block in 90 days.
Now we require a more enhanced solution, containing the entire block and the entire coinbase transaction hex, and the biblehash, using this info we will verify that if the block was solved at that particular second, that the pool would have been compensated and that the nonce is correct. We will now verify the solutions within 5 seconds also, so as to require real-time mining of the partial solution (preventing Hong Kong miners from pre-creating future solutions in the past).
After this release I will unlock the banned accounts that still exist (the Hong Kong accounts have been deleted) but you will need to re-create all your miners records.
So now that the upgrade is almost ready, Ill go into a little more detail as to why the 5 accounts were banned.
I have reason to believe one Hong Kong mining operation has been falsifying partial pool solution packets that hit as share solutions. Basically they are running the PCs in parallel and finding the distinct biblehash, and then leaving the thread in solo mining mode for a certain percentage of the time so as to trick the pool only when it asks how the thread is doing.
So this caused me to write a report on any miner who has not been solving actual blocks (IE MinerWhoFoundBlock) and therefore I banned all miners who have more than 10 machines pointed at the pool who have not found a block in 90 days.
Now we require a more enhanced solution, containing the entire block and the entire coinbase transaction hex, and the biblehash, using this info we will verify that if the block was solved at that particular second, that the pool would have been compensated and that the nonce is correct. We will now verify the solutions within 5 seconds also, so as to require real-time mining of the partial solution (preventing Hong Kong miners from pre-creating future solutions in the past).
After this release I will unlock the banned accounts that still exist (the Hong Kong accounts have been deleted) but you will need to re-create all your miners records.
So, Why I still can't login? You doubt that I am a miner of Hong Kong mining operation?
I believe this will be a big misunderstanding if you used a personal domain name to make a judgments.
Today's society, the domain not just for business use only, everyone can buy domain for personal to be more convenient to own-self.
Please do not ignore me, why just is my account can't login but my friend still normal mining.
Im sorry about that, I dont mean to come across as racist. I made a rash decision a few nights back and deleted the 5 Hong Kong accounts who appeared to be in my list who did not solve a block in 90 days. So, I might have deleted you.
Please PM your username and email and then you can start over, as long as you are running 1.0.8.6+.
Rob
January 25, 2018, 11:21:10 AM
I started by contacting uquid for debit card integration but still have not been able to find the status of visa integration for new communities:
Hi Rob,
Thank you for your contact.
We are currently changing our card vendor and this may take a few weeks. During this transition period we are not seeking to expand support for further cryptocurrencies. However, once we have our new card set up and distributed to all of our present customers, we will look at this.
Kind regards,
Mark Green
Customer Service Rep.
Skype : uquid.support
Hi Rob,
Thank you for your contact.
We are currently changing our card vendor and this may take a few weeks. During this transition period we are not seeking to expand support for further cryptocurrencies. However, once we have our new card set up and distributed to all of our present customers, we will look at this.
Kind regards,
Mark Green
Customer Service Rep.
Skype : uquid.support
January 25, 2018, 11:17:28 AM
"- Yobit: If you all give them a 5, I think we should go for it."
I agree.
As for the 0.1 BTC / approx $1200 USD payment to the YoBit exchange ... I will set up a group fund for contributions. Payments can be made in BBP, PayPal and several major credit cards. Each contributor will be refunded after the next proposal/budget process. I will post a link when the YoBit fund is up, should be ready later today.
January 25, 2018, 11:00:47 AM
Quote
So I should add at least 1 BBP to all my miners?
I can also add some miners to testnet if still needed? but I won't have any tBBP can someone help with that?
What is your tBBP wallet address?
January 25, 2018, 10:57:35 AM
Btw, update on 1.0.8.7:
1.0.8.6 is still all you need to pool mine properly (it includes the extended solution packet) and its also all you need to avoid crashes - for the sanctuaries (it includes the line of code that allows a Sanc to handle a missing vote. If you are wondering How that is even possible, its because Dash fixed the issue in Evolution while we fixed it in a version that was pre-evolution, and its slightly different code, but it works now). Anyway my point is 1.0.8.6 fixes the sanctuary crash and allows you to pool mine after block 27500.
1.0.8.7 only adds one debug field to getmininginfo. This field allowed me to install biblepay on some reference machines, and simulate a new block with a static timestamp and a 0 nonce - to see if the base block hash could be made unique. It worked, as long as you have more than 1 bbp in the wallet, the packet is unique. (Another words, a botnet with 0 in the wallet will have a propensity to mine less efficiently if they all create the same base blockhashes). The test succeeded, and I believe anyone mining on 1.0.8.6 with more than 1 bbp will be mining distinct packets (IE helping us drive up the difficulty and solve pool shares).
1.0.8.6 is still all you need to pool mine properly (it includes the extended solution packet) and its also all you need to avoid crashes - for the sanctuaries (it includes the line of code that allows a Sanc to handle a missing vote. If you are wondering How that is even possible, its because Dash fixed the issue in Evolution while we fixed it in a version that was pre-evolution, and its slightly different code, but it works now). Anyway my point is 1.0.8.6 fixes the sanctuary crash and allows you to pool mine after block 27500.
1.0.8.7 only adds one debug field to getmininginfo. This field allowed me to install biblepay on some reference machines, and simulate a new block with a static timestamp and a 0 nonce - to see if the base block hash could be made unique. It worked, as long as you have more than 1 bbp in the wallet, the packet is unique. (Another words, a botnet with 0 in the wallet will have a propensity to mine less efficiently if they all create the same base blockhashes). The test succeeded, and I believe anyone mining on 1.0.8.6 with more than 1 bbp will be mining distinct packets (IE helping us drive up the difficulty and solve pool shares).
So I should add at least 1 BBP to all my miners?
I can also add some miners to testnet if still needed? but I won't have any tBBP can someone help with that?
January 25, 2018, 10:43:17 AM
Quote
- Listing on the top 5 exchanges: Both fell through. I lost my personal 3.5btc on the deal
suprise? no ... listingcalendar coins to exchanges working ... January 25, 2018, 10:34:31 AM
Another big thanks goes out to Lichtsucher for his amazing efforts in generating the BBP apt package, especially the ARM version! I gave it a try on the Raspberry and it works like a charm. Before it took approx. 4-5 hours to install BBP on a Pi 3 (without GUI!) and then 1.5-2 hours for building every update, which was quite exhausting...
I see that you started a proposal for your work on the repository and package. I am far away from being a MN owner but I would definitely give you 10 upvotes for that.
I see that you started a proposal for your work on the repository and package. I am far away from being a MN owner but I would definitely give you 10 upvotes for that.
Thx a lot for your nice words, dave
And it's very good to know that the arm packages work, I couldn't test them and hoped the best. Sour feedback helps a lot 
January 25, 2018, 10:26:46 AM
Alright, the new core wallet is almost ready, but don't feel overly rushed as this version requires a mandatory upgrade for pool miners only before block 27500. If you have a lot of pool miners to upgrade you can start pulling down the linux version (1084) now, but I will announce the release soon (when windows is ready).
So now that the upgrade is almost ready, Ill go into a little more detail as to why the 5 accounts were banned.
I have reason to believe one Hong Kong mining operation has been falsifying partial pool solution packets that hit as share solutions. Basically they are running the PCs in parallel and finding the distinct biblehash, and then leaving the thread in solo mining mode for a certain percentage of the time so as to trick the pool only when it asks how the thread is doing.
So this caused me to write a report on any miner who has not been solving actual blocks (IE MinerWhoFoundBlock) and therefore I banned all miners who have more than 10 machines pointed at the pool who have not found a block in 90 days.
Now we require a more enhanced solution, containing the entire block and the entire coinbase transaction hex, and the biblehash, using this info we will verify that if the block was solved at that particular second, that the pool would have been compensated and that the nonce is correct. We will now verify the solutions within 5 seconds also, so as to require real-time mining of the partial solution (preventing Hong Kong miners from pre-creating future solutions in the past).
After this release I will unlock the banned accounts that still exist (the Hong Kong accounts have been deleted) but you will need to re-create all your miners records.
So now that the upgrade is almost ready, Ill go into a little more detail as to why the 5 accounts were banned.
I have reason to believe one Hong Kong mining operation has been falsifying partial pool solution packets that hit as share solutions. Basically they are running the PCs in parallel and finding the distinct biblehash, and then leaving the thread in solo mining mode for a certain percentage of the time so as to trick the pool only when it asks how the thread is doing.
So this caused me to write a report on any miner who has not been solving actual blocks (IE MinerWhoFoundBlock) and therefore I banned all miners who have more than 10 machines pointed at the pool who have not found a block in 90 days.
Now we require a more enhanced solution, containing the entire block and the entire coinbase transaction hex, and the biblehash, using this info we will verify that if the block was solved at that particular second, that the pool would have been compensated and that the nonce is correct. We will now verify the solutions within 5 seconds also, so as to require real-time mining of the partial solution (preventing Hong Kong miners from pre-creating future solutions in the past).
After this release I will unlock the banned accounts that still exist (the Hong Kong accounts have been deleted) but you will need to re-create all your miners records.
So, Why I still can't login? You doubt that I am a miner of Hong Kong mining operation?
I believe this will be a big misunderstanding if you used a personal domain name to make a judgments.
Today's society, the domain not just for business use only, everyone can buy domain for personal to be more convenient to own-self.
Please do not ignore me, why just is my account can't login but my friend still normal mining.
January 25, 2018, 10:24:07 AM
For all Sancturies!
I just end write page with masternodes notification center.
https://biblepay.eu/
After registration is ended, you can add masternode to monitoring.
Every one minute system compare actual and last status.
If it change, then system send email (one time only).
It's free for all!
any donation will be appreciated
If You will have some problem, please send information.
It will be writed from scratch so maybe there is some little bugs
I just end write page with masternodes notification center.
https://biblepay.eu/
After registration is ended, you can add masternode to monitoring.
Every one minute system compare actual and last status.
If it change, then system send email (one time only).
It's free for all!
any donation will be appreciated
If You will have some problem, please send information.
It will be writed from scratch so maybe there is some little bugs
Great job, Virus! I gave you one humble merit point and I will donate some BBP soon.
Thanks
This service I will not put as opensource, couse there is alot of my personal code used in many production services,
but some standalone system (with memcached or file based data) I will put very soon in open-source on github.
January 25, 2018, 10:20:57 AM
Btw, update on 1.0.8.7:
1.0.8.6 is still all you need to pool mine properly (it includes the extended solution packet) and its also all you need to avoid crashes - for the sanctuaries (it includes the line of code that allows a Sanc to handle a missing vote. If you are wondering How that is even possible, its because Dash fixed the issue in Evolution while we fixed it in a version that was pre-evolution, and its slightly different code, but it works now). Anyway my point is 1.0.8.6 fixes the sanctuary crash and allows you to pool mine after block 27500.
1.0.8.7 only adds one debug field to getmininginfo. This field allowed me to install biblepay on some reference machines, and simulate a new block with a static timestamp and a 0 nonce - to see if the base block hash could be made unique. It worked, as long as you have more than 1 bbp in the wallet, the packet is unique. (Another words, a botnet with 0 in the wallet will have a propensity to mine less efficiently if they all create the same base blockhashes). The test succeeded, and I believe anyone mining on 1.0.8.6 with more than 1 bbp will be mining distinct packets (IE helping us drive up the difficulty and solve pool shares).
1.0.8.6 is still all you need to pool mine properly (it includes the extended solution packet) and its also all you need to avoid crashes - for the sanctuaries (it includes the line of code that allows a Sanc to handle a missing vote. If you are wondering How that is even possible, its because Dash fixed the issue in Evolution while we fixed it in a version that was pre-evolution, and its slightly different code, but it works now). Anyway my point is 1.0.8.6 fixes the sanctuary crash and allows you to pool mine after block 27500.
1.0.8.7 only adds one debug field to getmininginfo. This field allowed me to install biblepay on some reference machines, and simulate a new block with a static timestamp and a 0 nonce - to see if the base block hash could be made unique. It worked, as long as you have more than 1 bbp in the wallet, the packet is unique. (Another words, a botnet with 0 in the wallet will have a propensity to mine less efficiently if they all create the same base blockhashes). The test succeeded, and I believe anyone mining on 1.0.8.6 with more than 1 bbp will be mining distinct packets (IE helping us drive up the difficulty and solve pool shares).
January 25, 2018, 10:14:26 AM
Does anyone know what is the status of CCEX fixing the wallet?
Got all my BBP stuck there for 2m now.
Crypto Brige is a great exchange 1 BTC is still a cheap price to pay for listing there.
In a few month it will be 5 BTC+ with the way things are going.
I tried to skype again this morning, no reply. Emails: No reply.Got all my BBP stuck there for 2m now.
Crypto Brige is a great exchange 1 BTC is still a cheap price to pay for listing there.
In a few month it will be 5 BTC+ with the way things are going.
Thanks for the update.
I am beginning to think that the whole 30+ day "vacation" is really a 30+ head start to close shop and leave the infrastructure on autopilot to get even more time to disappear.
Hope I am wrong on this.
January 25, 2018, 10:07:52 AM
Does anyone know what is the status of CCEX fixing the wallet?
Got all my BBP stuck there for 2m now.
Crypto Brige is a great exchange 1 BTC is still a cheap price to pay for listing there.
In a few month it will be 5 BTC+ with the way things are going.
I tried to skype again this morning, no reply. Emails: No reply.Got all my BBP stuck there for 2m now.
Crypto Brige is a great exchange 1 BTC is still a cheap price to pay for listing there.
In a few month it will be 5 BTC+ with the way things are going.
January 25, 2018, 10:05:42 AM
I'm really glad to see that over the last few hours the pool seems to make up on his deficit of hitting blocks; really nice coin output so far and big thanks to Rob for his dedication and his patience in keeping up with all the complaints.
Another big thanks goes out to Lichtsucher for his amazing efforts in generating the BBP apt package, especially the ARM version! I gave it a try on the Raspberry and it works like a charm. Before it took approx. 4-5 hours to install BBP on a Pi 3 (without GUI!) and then 1.5-2 hours for building every update, which was quite exhausting...
Now with the repository in hand I managed to start mining on the Pi 3 in less than 10 minutes! Another big advantage is that the package installation does not need the 1-2 GB "biblepay" folder, so it saves a lot of microSD space. (Unfortunately I am very busy at the moment, but when I find the time I will try to get BBP running on a minimal Ubuntu ARM system, maybe condensing the whole system to a 2 or 4GB SD card).
I see that you started a proposal for your work on the repository and package. I am far away from being a MN owner but I would definitely give you 10 upvotes for that.
God bless all the people dedicating time and effort on this project!
Regarding the pool "shares": I think right now they are at the absolute minimum of what they should be (I'm sorry, I have no clue about the technical or mathematical aspects going into this...) because from time to time my weak miners (DualCores or Raspberry Pi) disappear completely (but then show up again some time later...).
Another big thanks goes out to Lichtsucher for his amazing efforts in generating the BBP apt package, especially the ARM version! I gave it a try on the Raspberry and it works like a charm. Before it took approx. 4-5 hours to install BBP on a Pi 3 (without GUI!) and then 1.5-2 hours for building every update, which was quite exhausting...
Now with the repository in hand I managed to start mining on the Pi 3 in less than 10 minutes! Another big advantage is that the package installation does not need the 1-2 GB "biblepay" folder, so it saves a lot of microSD space. (Unfortunately I am very busy at the moment, but when I find the time I will try to get BBP running on a minimal Ubuntu ARM system, maybe condensing the whole system to a 2 or 4GB SD card).
I see that you started a proposal for your work on the repository and package. I am far away from being a MN owner but I would definitely give you 10 upvotes for that.
God bless all the people dedicating time and effort on this project!
Regarding the pool "shares": I think right now they are at the absolute minimum of what they should be (I'm sorry, I have no clue about the technical or mathematical aspects going into this...) because from time to time my weak miners (DualCores or Raspberry Pi) disappear completely (but then show up again some time later...).
Thanks for the update, and I agree, people need to realize Lichtsucher's PPM project is very valuable for Biblepay.
Regarding pool shares, I will make an attempt to see what the ratio of bad share submissions is next.
Our diff is really rising quickly over the last 2 days. Our diff is up from 500 to 1500 on average.
People need to realize how relative the leaderboard is. Now that 1.0.8.6 is out, a lot of the pool users are hitting the pool with complete packets, as you can see with the Hong Kong mining operation deleted from the pool - and it looks as if they never came back (we had 3400 miners, now we have 2345), the leaderboard changed slightly but its still relative.
January 25, 2018, 09:50:10 AM
Dear Rob and biblepay community,
I haven't had the chance to follow along with the posts for the past week or more, but I see there is still talk of getting on other exchanges. I would like for Rob and the community to give feedback on whether the idea of running our own exchange seems desirable or not? As for myself, I would like to see biblepay run its own exchange that closes for 24 hours over the weekend to respect the Sabbath. I think that would really bless this project and help it greatly. For a coin that wants to serve a Godly purpose, I think it is important to respect the Sabbath. I am not suggesting stopping the blockchain, but only halting trading for a 24 hour period. I don't know what the personnel or bugetary requirements for this would be, but I think it is worth considering. What does everyone think?
I haven't had the chance to follow along with the posts for the past week or more, but I see there is still talk of getting on other exchanges. I would like for Rob and the community to give feedback on whether the idea of running our own exchange seems desirable or not? As for myself, I would like to see biblepay run its own exchange that closes for 24 hours over the weekend to respect the Sabbath. I think that would really bless this project and help it greatly. For a coin that wants to serve a Godly purpose, I think it is important to respect the Sabbath. I am not suggesting stopping the blockchain, but only halting trading for a 24 hour period. I don't know what the personnel or bugetary requirements for this would be, but I think it is worth considering. What does everyone think?
With all respect to other beliefs, respecting the Sabbath is a jewish mandate. Us Christians respect Sundays, as they are the Lord's Day, the day Jesus resurrected, thus abrogating the Mosaic law.
Anyway I agree with the ones that think that running an exchange is calling for hackers, problems, and beyond the scope of BBP project.
My thoughts on these issues:
- The sabbath: I agree, Jesus ended the law and created the church and Christianity, and we are to pick up our cross daily. Its not necessary to keep one particular day holy, we are to follow all of Jesus' commandments.
- Running our own exchange: After seeing the viruses uploaded into childrens letters, and the hot wallet being stolen by the hackers, I am *very* reluctant to write an exchange in the pool. And as another said, US regulation is tough, so it could not be done by us.
- Yobit: If you all give them a 5, I think we should go for it.
- Ducks in a Row: Thats noble, but the issue Im facing now is we have no working exchanges and we need at least one LOL. People are trying to buy sancs, and I have to raise compassion.com funds once per month. So it is very high priority to get another one up. Although I agree, if we went on too many at once we would hogtie ourselves into limited updates.
- Listing on the top 5 exchanges: Both fell through. I lost my personal 3.5btc on the deal. I think we should work on yobit, coinexchange.io, and Blues NEXT decentralized exchange next. (Im working on the side to contact binance and hitbtc sr managers and reach them and give them documentation list of everything I went through to see if they will have compassion on us and list us on either exchange due to the fraud I experienced). Please dont write a lot of comments on the board about this, as I dont want to be polluted with things tying us to this- I would rather move past this issue and work up and onward.
January 25, 2018, 09:42:33 AM
January 25, 2018, 09:33:35 AM
We only have about 3 testers over here, could we please get at least 10? We dont need to set up sancs, so it should be very easy to test this:
http://forum.biblepay.org/index.php?topic=89.new#new
If ccex stays down for 10 more days, we could test this thoroughly and push it as a mandatory. If they come back up, we should wait until March to push it.
This next release fixes the 7 minute block targets and adds Proof-of-loyalty, etc.
The POL *has* to be thoroughly tested however.
http://forum.biblepay.org/index.php?topic=89.new#new
If ccex stays down for 10 more days, we could test this thoroughly and push it as a mandatory. If they come back up, we should wait until March to push it.
This next release fixes the 7 minute block targets and adds Proof-of-loyalty, etc.
The POL *has* to be thoroughly tested however.
January 25, 2018, 09:29:19 AM
Psalm 23
1 The Lord is my shepherd; I shall not want.
2 He maketh me to lie down in green pastures; He leadeth me beside the still waters.
3 He restoreth my soul; He leadeth me in the paths of righteousness for His name’s sake.
4 Yea, though I walk through the valley of the shadow of death, I will fear no evil; for Thou art with me; Thy rod and Thy staff, they comfort me.
5 Thou preparest a table before me in the presence of mine enemies; Thou anointest my head with oil; my cup runneth over.
6 Surely goodness and mercy shall follow me all the days of my life; and I will dwell in the house of the Lord for ever.
1 The Lord is my shepherd; I shall not want.
2 He maketh me to lie down in green pastures; He leadeth me beside the still waters.
3 He restoreth my soul; He leadeth me in the paths of righteousness for His name’s sake.
4 Yea, though I walk through the valley of the shadow of death, I will fear no evil; for Thou art with me; Thy rod and Thy staff, they comfort me.
5 Thou preparest a table before me in the presence of mine enemies; Thou anointest my head with oil; my cup runneth over.
6 Surely goodness and mercy shall follow me all the days of my life; and I will dwell in the house of the Lord for ever.
Jump to: