Topic: [ANN] KAPU - The first Archaeological Blockchain - - page 15. (Read 59097 times)

Finally. Look forward it.

I suggest to you to wait until the dev officially announcement about removal the signature campaign or at least until you receive Kapu coin, in order to your efforts will not be in vain

DEV!!  is it ok now to remove the signature? we are not going to be paid for these days for sure

thats great, I have sent you my kapu address in PM. Waiting for the payment

Guys tell you that in order to receive the Bonus / Bounty I ask you to write in private your kapu wallet adress who will forward to the community manager

Yes, I have not found a similar project at present, it is very unique, the protection of the world heritage will receive its special care, I believe that its development prospects are bright.

Correct! How can you send coin?

This project interesting because Kapu aims to preserve the finds all around the world using the Blockchain technology. Also i think this project not have competitor yet so this coin can growing rapidly

thank you to the team and dev from the project because I saw in the announcement of the participants have token comments from the project and I will wait for further news from the project hoping to immediately have a description of the distribution for the participants who are project

I looked at this thread, and I found that the combination of blockchain and archaeology for the first time is interesting. I will continue to pay attention to its development, although I am not involved in the ico.

If I remember well we were not asked addresses at time of registration for any of these mentioned campaigns. How the distribution is possible in absence of addresses of participants ? I hope this was about the calculation of stakes and tokens and we will be contacted for addresses to receive the tokens.

It is understandable that sometimes these delays happen but good thing is this communication and announcement about the starting of distribution today. Kapu is promising and original idea based project which will see huge success. Team is very active and professional in handling everything.

Signature Bounty 44923.3 Kapu

Facebook Campaign 4182.78 Kapu

Twitter Campaign 3383.08 Kapu

Total 52489.16 Kapu


Sorry the delay but for the calculations it took a while .. Today we will distribute all the KAPUs as from Excel spreadsheet

Hello fellow Kapuans, Richard and Goose consider ourselves new to the crypto world, however we have both embraced it whole hearted in the past 6 months and haven’t looked back.
Goose has been tinkering with computers ever since I was given a Commodore 64 to play with at a very young age. Goose is currently in the financial service sector as a risk management specialist.
Richard has come from a different field being in that of mechanical engineering & estimating industry, where risk and calculated costs are always taken into account as well of profits within the area.
We are both very excited about KAPU and think the archeological twist is a great one. We are proposing running 2 delegates (1-off private, 1-off public). We believe in rewarding those that are within our pool, we want to create a community within the pool where those that do vote for us can approach us if they have any queries as we look to improve the culture as a whole for those new to the DPoS world.
You can reach either of us on slack @goose or @riichard if you have any questions about our proposal
OUR PROPOSAL
We are proposing running 2 delegate nodes as follows:

Goose (private delegate)
0_1508542131278_5f406ac3-cf31-4a9e-8b9d-95c2540c1109-image.png

For high balance wallets (>15k)
Weekly payout (until script automation then daily)
Initial 20% share rate which will go up as KAPU price does
Looking for 2-25 voters (>25 go on waitlist) to maintain good dilution rate
Initial fidelity of 7 days to prevent pool hopping (will reduce to 24 hours after daily distributions start)
No min/max payment, tx fees covered
Duck (public delegate)


All wallets welcome especially small ones
Weekly payout
Fidelity of 7 days to prevent pool hopping
Initial 20% share rate which will go up as KAPU price does
Will only distribute rewards to wallets up to 15K (over 15k only get rewards on 15k balance) to be fair to small wallets
No min payment, tx fees covered
In addition, we will be reserving 2.5% of forged rewards from each delegate (5% collectively) and are planning to build a KAPU faucet to spread the KAPU love far and wide both within and outside the community to get the word out. It is currently in process of being developed but we hope to make ~42 KAPU a day available for anyone that wants KAPU.
Other Details:
NETWORK SETUP
We plan to run 3 nodes (2 mainnet, 1 devnet). Note: We plan to upgrade as needed to meet the needs of the network
Goose Node
Host: Vultr
CPU: 2 vCore
RAM: 4GB
DISK: - 60GB
Duck Node
Host: Vultr
CPU: 2 vCore
RAM: 4GB
DISK: - 60GB
Back-up for goose/duck - Vultr – as needed
Devnet Node
Host: Personal
CPU: 4 core
RAM: 8GB
DISK: 120GB
CONCLUSION
Thanks for reading – vote for us if you can!

The team said on the slack channel that kapu coin still distribution, maybe coin for bounty hunter will distributed after investors received their coin. So please be patient, i hope distribution all coin can finish this week

Very good slack channel thanks . When distribuited kapu ? .

I suggest to you join slack channel because kapu community active there, the devs also active there so they will help you as fast as possible. Here it's : http://slack.kapu.one/

hi all, how i can import my wallet from Windows to Mac, i do add address with pass but my coins are 0...

please tell me where you your wallet was prescribed to receive coins from the bounty

Hello fellow Kapuans, Richard and Goose consider ourselves new to the crypto world, however we have both embraced it whole hearted in the past 6 months and haven’t looked back.
Goose has been tinkering with computers ever since I was given a Commodore 64 to play with at a very young age. Goose is currently in the financial service sector as a risk management specialist.
Richard has come from a different field being in that of mechanical engineering & estimating industry, where risk and calculated costs are always taken into account as well of profits within the area.
We are both very excited about KAPU and think the archeological twist is a great one. We are proposing running 2 delegates (1-off private, 1-off public). We believe in rewarding those that are within our pool, we want to create a community within the pool where those that do vote for us can approach us if they have any queries as we look to improve the culture as a whole for those new to the DPoS world.
You can reach either of us on slack @goose or @riichard if you have any questions about our proposal
OUR PROPOSAL
We are proposing running 2 delegate nodes as follows:

Goose (private delegate)

-   For high balance wallets (>15k)
-   Weekly payout (until script automation then daily)
-   Initial 20% share rate which will go up as KAPU price does
-   Looking for 2-25 voters (>25 go on waitlist) to maintain good dilution rate
-   Initial fidelity of 7 days to prevent pool hopping (will reduce to 24 hours after daily distributions start)
-   No min/max payment, tx fees covered

Duck (public delegate)

-   All wallets welcome especially small ones
-   Weekly payout
-   Fidelity of 7 days to prevent pool hopping
-   Initial 20% share rate which will go up as KAPU price does
-   Will only distribute rewards to wallets up to 15K (over 15k only get rewards on 15k balance) to be fair to small wallets
-   No min payment, tx fees covered
In addition, we will be reserving 2.5% of forged rewards from each delegate (5% collectively) and are planning to build a KAPU faucet to spread the KAPU love far and wide both within and outside the community to get the word out. It is currently in process of being developed but we hope to make ~42 KAPU a day available for anyone that wants KAPU.
Other Details:
NETWORK SETUP
We plan to run 3 nodes (2 mainnet, 1 devnet). Note: We plan to upgrade as needed to meet the needs of the network
Goose Node
Host: Vultr
CPU: 2 vCore
RAM: 4GB
DISK: - 60GB
Duck Node
Host: Vultr
CPU: 2 vCore
RAM: 4GB
DISK: - 60GB
Back-up for goose/duck - Vultr – as needed
Devnet Node
Host: Personal
CPU: 4 core
RAM: 8GB
DISK: 120GB
CONCLUSION
Thanks for reading – vote for us if you can!