A historical even we did not know about has recently been uploaded to the English-language Wikipedia. It’s all about the War between the Vicuñas and the Basques for the control of Potosí, in modern-day Bolivia, between 1622 and 1625. So what happened? Well, we’re not going to go too far into it ourselves, as we’re attaching some great reading to this article, but we did not to perhaps provide a bit of context to explain why this area was so important in the 17th century.
Potosí is in southern Bolivia at an elevation of 4,067 m or 13,343 ft, and is one of the three highest cities in the world. It owes its existence to the extraordinary silver deposits inside the mountain that gave the town its name. Thanks to them, Potosí became one of the great wealth producers of the Spanish Empire for almost two centuries, until the mines ran out. In 1650, this city was the largest in the Americas, and one of the largest in the world, with 160,000 residents (more than London or Paris). And, that city and that wealth were under the control of the Basques, to the point that:
El trabajo organizado, constante y tenaz de los vascos y su consecuente poderío económico, despierta la envidia en otros grupos étnicos españoles y en los hijos de españoles nacidos en América (criollos), que bajo el liderazgo de Alonso de Ibáñez (1.617) se rebelan contra el orden establecido, provocando la guerra entre vicuñas (criollos) y vascongados.
The organized, constant, and tenacious labor of the Basques and their consequent economic power awoke jealousy among other Spanish ethnic groups and in the children of the Spaniards born in the Americas (creoles), who, under the leadership of Alonso de Ibáñez, rebelled in 1617 against the established order, triggering a war between the vicuñas (creoles) and the Basques. (Bolivia en la red. Departamento de Potosí)
So, the Spaniards and their creole children rebelled agains tthe control the Basques had of the city’s mines and institutions. They had achieved this control thanks to their ability to set up the mines, to organize as “the Basque nation” (the first Guild of Aranzazu in all the Americas was in Potosí), and their skilled use of the rights afforded them by their status as hidalgos. This all meant that in a time when there was no equality (even for the conquistadors themselves), the Basques were able to rise to a very favorable position, despite their small numbers among the colonial population as a whole.
This all means, therefore, that we’re not talking about “good guys” and “bad guys”, but rather the fact the leaders of one group of colonists, the Vicuñas, who were the largest group, did not accept that the very small Basque community had managed to amass almost complete control of the mines and public offices in the town. It wasn’t a struggle between owners and workers, but rather groups of power who wanted control of the means of production and the positions of power in the city government. Perhaps the most important matter here is to understand the differences in attitude and ability at the time that allowed the Basque community to achieve this highly influential position.
The Basques did not “conquer” the mines: they created the business that exploited them and made the profitable, for themselves and for the Crown, for whom having the guarantee of continuous extraction and transformation of the wealth that came out of Potosí Mountain was fundamental in their plans to expand and dominate Europe. The Basques shone as businessmen and traders in the New World colonies.
And we do mean between Spaniards and Basques, because among the latter were also Basques from north of the Pyrenees (it is well known that many Northern Basques crossed the mountains and passed themselves off as Southerners in order to be able to emigrate to South America). The confrontation lasted for three years, and the final result was that the Basques maintained their position, and the leaders of the vicuñas became outlaws.
Two interesting factoids:
First there was the fact that on the Basque side, alongside the “members of the Basque nation” (people from Biscay, Alava, Gipuzkoa, Navarre, and the mountains) were the Catalans. And secondly, we can see how, in the middle of the war, one of the Vicuña leaders, Juan Fernández de Tovar, decided to take the vows. It seems his sudden conversion had a lot to do with a 20,000 peso debt (quite a fortune) that he couldn’t pay. Perhaps seeing that he couldn’t get quick access to the wealth of the Basques, which would have freed him of his debt, made him see the light, and he joined the Franciscan order.
Depiction of the Cerro del Potosí
As we said, this is the first time we’ve found information about this historical event, but it wasn’t hard to find more resources that cover it, which we’re going to include in this entry should anyone’s interest have been piqued (like ours was).
We hope you enjoy learning about this quite curious event.
Wikipedia – 28/8/2011 – Encyclopedia (English-language edition)
Basque-Vicuña war
The Basque-Vicuña war (Spanish: Guerra de Vicuñas y Vascongados) was an armed conflict in Alto Peru, present-day Bolivia, that lasted between June 1622 and March 1625, fought between Basques and “Vicuñas” (an informal term for non-Basque Spaniards, a name obtained through the habit of wearing hats made of vicuña skins).Competition over the control of the silver mines in Potosí, Lípez and Chichas surged in the early 17th century, pitting Basques and Vicuñas against each other.[2] The Vicuñas had initially employed legal and political measures attempting to block the Basque attempts to monopolize control over the Cabildo (municipal government) of Potosí and the silver mining sector. However, these efforts did not yield results. Violent incidents began in 1615, and escalated in 1622 following the assassination of a Basque of a street in Potosí.
This website uses cookies so that we can give you the best possible user experience. Cookie information is stored in your browser and performs functions like recognising you when you return to our website and helping our team understand which website areas you find most interesting and useful.
Necessary cookies activate basic functions like navigation and access to secure website areas. Without these cookies, the website cannot work properly.
Cookie
Type
Duration
Description
cookielawinfo-checkbox-necessary
persistent
1 year
This cookie is set by the GDPR Cookie Consent plugin. It is used to store user consent for the cookies in the “Necessary” category.
cookielawinfo-checkbox-non-necessary
persistent
1 year
This cookie is set by the GDPR Cookie Consent plugin. It is used to store user consent for the cookies in the “Non-Necessary” category.
PHPSESSID
session
End of browser session
This cookie is native to PHP and allows the website to save serialized status data. On this website, it is used to establish user sessions by passing status data via a temporary, or session, cookie. This cookie has no established expiration because it disappears when the website is closed.
viewed_cookie_policy
permanent
1 year
This cookie is placed by the GDPR Cookies Consent plug-in and is used to store whether the user has consented to the use of cookies or not. It stores no personal data.
__cfduid
permanent
1 month
Established by the CloudFlare service to identify trusted web traffic.
Marketing cookies are used to track website visitors. The aim is to display adverts that are relevant and appealing to the individual user.
Cookie
Type
Duration
Description
1P_JAR
persistent
1 month
This cookie is used to transfer data to Google.
DSID
persistent
1 hour
Established by Google, if you have started a session with your Google account on another device, this is used to link your activity between devices and coordinate ads that appear on them and to convert them.
fr
persistent
3 months
This cookie is necessary for the Facebook “Like” button to work.
IDE
persistent
2 years
Used by Google DoubleClick, it stores information about the way the user uses the website and any other ads before visiting the website. It is used to present the user with ads that are relevant according to the user’s profile.
mc
persistent
1 year
QuantCast platform cookie for granular audience measurements. It stores no personal data, only user identifiers and their browsing.
NID
persistent
6 months
The NID cookie contains a unique ID that Google uses to remember your preferences and other information, such as your preferred language, the number of search results you want shown per page (for example, 10 or 20), and whether you want the Google Safe Search filter activated.
uid
persistent
1 year
This cookie is used to anonymously measure the number and behavior of the visitors to the website. The data include the number of visits, the average duration of visit to the website, visited websites, etc., in order to understand the user’s preferences better with regards to targeted ads.
VISITOR_INFO1_LIVE
permanent
5 months
This cookie is placed by YouTube. It is used to trace the information of the YouTube videos that are embedded in a website.
_fbp
permanent
1 day
Used by Facebook to offer a line of advertising products, such as real-time offers from third-party advertisers.
Unclassified cookies are cookies that we are in the process of classifying, together with the providers of individual cookies.
Cookie
Type
Duration
Description
cref
persistent
1 year
Contains data on user navigation interaction and time spent on the website and its sub-pages. This data is used to optimize the relevance of advertisements and for statistical purposes.
d
persistent
3 months
Collects anonymous data on the user's visits to the website, such as the number of visits, average time spent on the website and what pages have been loaded with the purpose of generating reports for optimizing the website content.
i
persistent
1 year
Registers anonymized user data, such as IP address, geographical location, visited websites, and what ads the user has clicked, with the purpose of optimizing ad display based on the user's movement on websites that use the same ad network.
KADUSERCOOKIE
persistent
3 months
Registers a unique ID that identifies the user's device during return visits across websites that use the same ad network. The ID is used to allow targeted ads.
KTPCACOOKIE
persistent
1 day
Registers a unique ID that identifies the user's device during return visits across websites that use the same ad network. The ID is used to allow targeted ads.
na_id
persistent
13 months
Used to recognize the visitor upon re-entry. This allows the website to register the visitor's behavior and facilitate the social sharing function provided by Addthis.com.
na_rn
persistent
13 months
Used to recognize the visitor upon re-entry. This allows the website to register the visitor’s behavior and facilitate the social sharing function provided by Addthis.com.
na_sc_e
persistent
1 month
Used to recognize the visitor upon re-entry. This allows the website to register the visitor’s behavior and facilitate the social sharing function provided by Addthis.com.
na_sr
persistent
1 month
Used to recognize the visitor upon re-entry. This allows the website to register the visitor’s behavior and facilitate the social sharing function provided by Addthis.com.
na_srp
persistent
1 day
Used to recognize the visitor upon re-entry. This allows the website to register the visitor’s behaviour and facilitate the social sharing function provided by Addthis.com.
na_tc
persistent
13 months
Used to recognize the visitor upon re-entry. This allows the website to register the visitor's behavior and facilitate the social sharing function provided by Addthis.com.
ouid
persistent
13 months
Sets an ID-string for the specific visitor. This is used to recognize the visitor upon re-entry. This allows the website to register the visitor's behavior and facilitate the social media sharing function provided by Addthis.com.